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

DEVELOPER SETUP / BETA

One project.
One shared task.

Gonu’s engineering clients connect to the existing Gonu account and Agent API. Start with a repository explanation, then plan a change.

Desktop

Use an available Gonu Worker build to open your repository. Local execution requires your approval for writes and commands.

Check release availability →

VS Code extension

The extension is currently a local development beta. A Marketplace release is not published here. It supports shared tasks, selected code, diff approval and file checkpoints.

Request beta access →

Command line

The CLI is currently distributed from source for testing. It uses the same Agent API and supports task inspection, local repository context and interactive approvals.

Request CLI beta access →

Your first useful task

  1. Sign in with your existing Gonu account.
  2. Choose a Gonu model enabled for your plan, or select an installed Ollama model in a supported local client. No personal API key is required for Gonu-provided models; your plan allowance applies.
  3. Open an authorized repository and allow relevant source excerpts to be used.
  4. Run Ask: “Explain this project.” Check the returned file references.
  5. Use Plan for a proposed change. Review each diff and command before approving.
  6. Inspect the same session in Engineering tasks. Run tests and review their exit codes before publishing.

Local Ollama inference runs on your machine; Gonu API still receives selected task context for orchestration and history. ASK, PLAN and REVIEW are read-only. AUTO still requires action approvals. File checkpoints protect individual edits; they do not undo arbitrary terminal commands. Cross-surface history is shared, while local files remain on their original machine.

GitHub App execution requires an installed App, an allowed repository and an enabled isolated executor. Check the GitHub guide for approval gates and availability. A standalone Code-OSS IDE distribution is not offered here. A successful Agent turn is not a production-readiness certification.

Open engineering tasks →

CLI walkthrough · VS Code walkthrough · GitHub workflow · Agent modes and approvals