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
06 / Requirement to SystemPartial implementation

One requirement. A reviewable path to code.

Hand a requirement to the existing engineering pipeline for planning, implementation, checks and review in your project.

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. Choose a system task, describe the requirement and name the behavior that must remain unchanged.

  2. Review the plan and approve file changes or commands through the existing execution flow.

  3. Check the final diff, recorded validation and unresolved setup. Open a running preview only if one actually exists.

g.Requirement to SystemSAMPLE
ILLUSTRATIVE WORKSPACE

Requirement / Subscription settings

Feature

Show cancellation date

Reuse

Existing billing and account system

Acceptance

No paid access after expiry

Illustrative requirement, not a completed billing integration.
Step 1 of 3

A useful first request

Add subscription status to this existing application. Reuse its billing system, plan first, and validate with the existing tests.

MADE FOR Developers building an existing product

When it earns its place.

Develop a focused feature across the existing application while preserving its authentication, billing and design conventions.

THE USEFUL RESULT

A controlled implementation with explicit configuration and delivery gaps.

Repository content is untrusted input. Production, messaging and access changes still need their own permission.

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

  • Requirement handoff to the existing build/test/self-fix/review pipeline.
  • Shared task identity, permissions, budgets and artifacts.

Not available yet

  • Universal app and cloud provisioning.
  • Automatic secrets configuration and deployed previews.
  • Live-provider end-to-end acceptance for each intended stack.

GET READY

Start with the right context.

  • An authorized repository with working build and test prerequisites.
  • A model, task budget and permission to perform each proposed action.

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.

Prepare a system task

Practical guides

Ask, Plan, Build, Debug & ReviewDesktop WorkerReview diffs & restore checkpointsDesktop WorkerEngineering Brain: your software and its historyWeb workspaceDiscuss your team's setup