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
01 / Living Engineering BrainBeta workflow

Understand the code. Keep the reasons.

Connect repository structure with shared decisions, incidents and selected team knowledge in one inspectable map.

Explore the demo Open repository map

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

Interactive demoWhen to use itCurrent capabilitiesSetup & guides

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 Engineering Brain, select your workspace and project, then scan the authorized repository.

  2. Create a shared decision or incident. Reference a file or existing document and assign an owner when appropriate.

  3. Search the map and read each source, date and revision before preparing a change.

g.Living Engineering BrainSAMPLE
ILLUSTRATIVE WORKSPACE

Repository / sample-checkout

src/checkout.ts

Imports payment-client.ts

tests/checkout.test.ts

References checkout.ts

Deployment config

Declared project configuration

Import links are static candidates, not observed production traffic.
Step 1 of 3

A useful first request

Explain how checkout works. Cite the relevant files and recorded decisions, and list what the evidence does not tell you.

MADE FOR Developers, technical leads and engineering teams

When it earns its place.

Before changing a service, find the relevant files, recorded decisions and people explicitly assigned to the work.

THE USEFUL RESULT

A navigable project map and traceable context for the next task.

Sources are checked against current workspace and project access. Scanning does not upload a device-local repository or call a model.

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

  • Incremental source metadata and import candidates.
  • Shared records, permitted documents and consented transcript sources.
  • Versioned evidence and explicit ownership relationships.

Not available yet

  • Automatic live Jira, Slack and incident ingestion.
  • A complete semantic graph of production services and infrastructure.

GET READY

Start with the right context.

  • An authorized managed repository with accessible files.
  • A repository scan and deliberately shared decisions or imported documents.

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.

Open repository map

Practical guides

Engineering Brain: your software and its historyWeb workspaceUnderstand a repositoryDesktop WorkerDiscuss your team's setup