Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
14 / Software Self-HealingPartial implementation

From a signal to a controlled repair.

Record a fresh measurement, evaluate a threshold and prepare an incident-linked repair draft for reviewed execution.

Public demo · no login needed. Real workspace use requires sign-in, project access and a configured release.

TAKE A LOOK INSIDE

See how the workflow fits together.

Interactive illustration

All screens use synthetic sample content. Clicking through this demo does not run a model, access your files, change an account or use your allowance.

  1. Create a metric record with a value, unit and observation time. Configure its threshold in Maintenance & incidents.

  2. Inspect a threshold finding and its repair draft. Confirm the problem before starting reproduction or editing.

  3. Use existing checks and reviews to validate the repair. Production canary and rollback steps require future adapters and acceptance.

g.Software Self-HealingSAMPLE
ILLUSTRATIVE WORKSPACE

Signal / Checkout duration

Measurement

Supplied by an authorized user

Freshness

Observation time required

Threshold

Configured above/below rule

The current feature is not a live telemetry connection.
Step 1 of 3

A useful first request

Review this threshold incident. Propose a reproduction and fix with evidence, and keep all production actions outside the approved local scope.

MADE FOR On-call engineers and platform teams

When it earns its place.

Give a team a clear starting point for an incident workflow while production deployment remains under explicit control.

THE USEFUL RESULT

A controlled incident-to-repair starting point; production self-healing remains incomplete.

A metric or retrieved incident cannot authorize deployment. Production access needs separate policy and implementation.

CURRENT CAPABILITIES

Know exactly what to expect.

The described foundation is implemented. The advanced actions listed as pending are not available yet.

Implemented in the beta

  • Fresh supplied metrics, threshold incidents and repair drafts.
  • Connection to the existing controlled reproduction and verification flow.

Not available yet

  • Live telemetry ingestion and automated root-cause detection.
  • Canary deployment, traffic shifting, measured validation and automatic production rollback.
  • These require additional implementation, not just credentials.

GET READY

Start with the right context.

  • A fresh, explicitly supplied measurement and reviewed threshold policy.
  • An authorized project and existing controlled execution setup for repair work.

Brain workflows require the matching API/Web release and an authorized managed project. The model, executor and integrations must be configured for the task you choose. Opening a demo does not enable an integration.

Inspect incidents & repair drafts

Practical guides

Engineering Brain: your software and its historyWeb workspaceVerified fixes, memory and private reviewsWeb workspaceDiscuss your team's setup