GitHubDocsCocode Nut
Checking sign-in status
Documentation中文

Start here

Start with your first Cocode task

Quickstart

Quickstart

Guides

GUI desktop workspaceTUI terminal interface

Core concepts

Core conceptsPermissions and approvals

Models and teams

Cocode Nut model serviceTeams and organizations

Developers

API overview

Reference and help

CLI and shortcuts referenceTroubleshooting
Cocode Docs / Troubleshooting

Troubleshooting

Collect safe diagnostics first

cocode doctor
cocode host status --json

When reporting an issue, include OS, Cocode version, GUI/TUI entry point, time, and redacted output. Do not upload API keys, OAuth links, cookies, provider secrets, or complete session logs.

The installation does not start

Confirm that the package matches your operating system and architecture, then reopen the app or terminal. For CLI issues, start with:

cocode --help

TUI also requires Node.js 22.19.x+ and a real TTY; CI, pseudo-terminals supplied by some IDEs, and pipes may not provide the required capabilities.

Login fails or stays in the browser

Finish browser sign-in and return to Cocode. If a device code expires or is denied, start login again. Never paste an authorization URL, cookie, or API key into a public issue.

For Supervisor unavailable, RUNTIME_*, or a TUI stuck in starting, run cocode host status --json; if needed, run cocode host stop --force and retry.

Model requests fail

Check available credits and whether the model is still present in the plan and catalog. If you see interactive_session_required, use an entry point that supports interactive sessions. For rate limits, wait for the window to recover or reduce concurrency. Error families include AUTH_*, RUNTIME_*, COMMAND_*, SESSION_*, CONFIG_*, and IO_*; preserve the code, time, and redacted context.

Documentation is continuously updated.support@cocode.agency