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
09 / Safe RollbackBeta workflow

Recover the files. Preserve your work.

Preview a grouped rollback of recorded file edits, check for later changes and approve the exact restoration plan.

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. Open Replay, undo & skills, select the execution and request a file rollback preview.

  2. Compare the current file state with the recorded post-change hash. Later edits cause restoration to stop.

  3. Approve a fresh exact preview only when safe. An inverse journal preserves current state for reviewed recovery if interrupted.

g.Safe RollbackSAMPLE
ILLUSTRATIVE WORKSPACE

Rollback / Recorded files

Before task

Developer's existing work

Agent change

Recorded checkpoint

Scope

File edits only

Terminal side effects are outside file checkpoint scope.
Step 1 of 3

A useful first request

Show the file rollback plan for this task and identify any changes or external side effects that cannot be restored automatically.

MADE FOR Developers reviewing agent changes

When it earns its place.

Recover from an agent edit while keeping the developer's work that existed before the task began.

THE USEFUL RESULT

A scoped recovery plan with conflict checks and explicit limits.

Only an authorized task owner can approve writes. The tool never presents an unrestricted Undo Everything action.

CURRENT CAPABILITIES

Know exactly what to expect.

Implemented beta workflow. Your server needs the matching release, project access and required setup.

Implemented in the beta

  • Grouped checkpoint preview and hash-based conflict refusal.
  • Explicit file restore with an inverse recovery journal.
  • Preservation of earlier uncommitted developer work.

Not available yet

  • Database, cloud, ticket and deployment compensation adapters.
  • Automatic recovery of a partially applied rollback group.

GET READY

Start with the right context.

  • Recorded file checkpoints on the originating executor.
  • A stopped task, write approval and unchanged current file hashes.

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 file recovery

Practical guides

Review diffs & restore checkpointsDesktop WorkerEngineering Brain: your software and its historyWeb workspaceDiscuss your team's setup