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
Desktop Worker

Review diffs & restore checkpoints

Inspect proposed file changes and use recorded snapshots for deliberate recovery.

Open the Worker download pageExplore the example

WHEN IT HELPS

Put it to work.

Keep existing uncommitted work in view, review multiple-file changes and recover a file when a task goes in the wrong direction.

Before you begin

  • An actual local file change or checkpoint for the selected task.
  • The same authorized local folder and no conflicting unsaved editor buffers.

WALK THROUGH IT

See the workflow, step by step.

Interactive example

Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.

  1. Open the affected file’s before/after preview. Check additions, removals and permissions before approving a write or final review.

  2. Inspect the changed-file list and actual test evidence. Approving the local group is separate from authorizing a Git commit or remote publication.

  3. Open Checkpoints, select recorded versions and review the current/proposed restore diff. Confirm only that exact restore. If files change during review, inspect a fresh preview.

gonu / Review diffs & restore checkpointsSAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 3

Example diff / src/session.ts

Beforereturn session !== null;
Proposedreturn session !== null && !session.expired;
Review questionDoes the existing session type have an expired field?
Example only · your real screen shows your own data.
Step 1 of 3

THE USEFUL RESULT

What you should leave with.

A reviewed local change or a recorded file recovery with its actual result.

Know the boundaries.

  • File snapshots do not undo arbitrary terminal commands, database writes or remote actions.
  • Multiple-file restore is sequential, not an atomic rollback. A partial result must be inspected before further recovery.

IF SOMETHING DOESN’T WORK

The restore preview is stale or blocked.

Save or resolve unsaved editor buffers and reopen the preview. Do not force a stale approval over newer file changes.

Contact support