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
Source beta

Gonu CLI

Use shared tasks and approved local repository tools from a terminal.

Request source beta accessExplore the example

WHEN IT HELPS

Put it to work.

Ask, plan, review and inspect work without leaving your development terminal.

Before you begin

  • Access to the CLI source beta and adjacent reviewed SDK source; Node.js 22 or newer.
  • A configured Gonu backend/account. Interactive authentication needs a supported OS credential store.

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. Build the SDK first, then install and build the CLI as described in its README. Check help before running a repository task.

  2. Use the device-login command and approve the matching code in your Gonu account. Ask about an authorized repository before making changes.

  3. Use the session/task commands for recorded work. Review file/command approvals interactively. Use JSON output where appropriate for inspection.

gonu / Gonu CLISAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 3

Terminal / Source-checkout commands

SDK foldernpm ci --ignore-scripts && npm run build
CLI foldernpm ci --ignore-scripts && npm run build
Helpnode dist/cli.js --help
Example only · your real screen shows your own data.
Step 1 of 3

THE USEFUL RESULT

What you should leave with.

Terminal access to the existing account, project/session APIs and authorized local execution.

Know the boundaries.

  • An npm release is not promised here. Do not use a guessed global install command; obtain the current beta distribution instructions.
  • Headless Auto does not grant blanket write permissions. Local commit/push and configured GitHub job publication are different paths.

IF SOMETHING DOESN’T WORK

Login cannot save the session.

Check OS credential-store availability: macOS Keychain, Linux Secret Service or Windows Credential Manager. Use the documented secure headless setup when there is no store; never save tokens in a repository.

Contact support