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
02 / Software Time MachineBeta workflow

Every workaround has a history.

Explore recorded Git changes, repository snapshots and revisions of shared decisions to understand how a system evolved.

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. In Decisions & history, inspect the history of a project-relative file.

  2. Open a shared record and its revisions. Compare the recorded reasoning with the code changes.

  3. Use Future Scenarios to explicitly exclude a decision from an impact question, then review the assumption with the team.

g.Software Time MachineSAMPLE
ILLUSTRATIVE WORKSPACE

History / src/payment-client.ts

Earlier commit

Introduced bounded retries

Later commit

Added timeout handling

Current file

Inspect actual source before changing

Illustrative sequence; actual history comes from Git.
Step 1 of 3

A useful first request

Why was this retry added? Separate what the commit and decision records prove from what remains an assumption.

MADE FOR Maintainers and new project members

When it earns its place.

Review an old workaround before removing it, or give a new teammate the background behind a design choice.

THE USEFUL RESULT

A reviewable history, with gaps left visible.

Historical views use sources you can access now; they do not restore revoked permissions.

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

  • Bounded real Git history and saved repository snapshots.
  • Shared decision and incident revisions.
  • Explicit exclusions for counterfactual questions.

Not available yet

  • Complete historical reconstruction of every connected document.
  • Automatic generation of a proven alternate architecture.

GET READY

Start with the right context.

  • A managed project with accessible Git history.
  • Saved repository snapshots or versioned shared records.

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.

Explore decisions & history

Practical guides

Engineering Brain: your software and its historyWeb workspaceEngineering task evidenceWeb workspaceDiscuss your team's setup