Tutu CLI: every coding AI from one command
Install once, then just run tutu claude or tutu codex.
Your key is filled in when you copy
bash <(curl -fsSL 'https://api.tutucompute.com/v1/launch?lang=en' -K - <<< 'header = "Authorization: Bearer …"')
Get started in three steps
- 1
Install the Tutu CLI
- 2
Run tutu claude (or codex / opencode / hermes)
- 3
Click Allow in your browser the first time
Install
Run this line in a terminal on macOS / Linux, or in PowerShell on Windows.
macOS / Linux
curl -fsSL https://api.tutucompute.com/tutu | sh Windows (cmd)
powershell -NoProfile -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor 3072; irm https://api.tutucompute.com/tutu.ps1 | iex" Windows (PowerShell)
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor 3072; irm https://api.tutucompute.com/tutu.ps1 | iex Then run:
tutu claude Supported tools
Four main ones; the other tools on the connect page also open with tutu <name>.
- Claude Code
tutu claudeEvery model tier, sub agents included, points here; file edits are allowed by default and read-only commands don't ask. - Codex
tutu codexStarts with a model catalog, so Codex knows each model's real context length; no ChatGPT connectors. - OpenCode
tutu opencodeMain model and title generation both go here; if your copy is too old, a new one is installed alongside and yours stays untouched. - Hermes Agent
tutu hermesIts config is written for you; if git is missing, it is installed first.
Why not just set environment variables
| Tutu CLI | Setting env vars yourself | |
|---|---|---|
| Missing tools | Installed for you | Install them yourself |
| Key | Signed in automatically, never on the command line | Keep it and paste it yourself |
| Model changed on the web | Applies on the next launch | Set it again |
| Tool version too old | A new copy is installed alongside | Upgrade it yourself |
| Codex model window | Model catalog passed automatically | Default value |
Security
- Your Key never appears on the command line, so it isn't visible in the process list.
- Sign-in credentials stay on your own computer; revoke them in Key management and this computer is signed out.
- Updates check the download's sha256 and are not applied if it doesn't match.
- It runs no server and shares no compute; to share compute, tutu node installs the Tutu Compute Node separately (it asks first).
Common commands
- tutu: sign-in status and the versions of the four tools
- tutu login / tutu logout: sign this computer in / out
- tutu update: update to the latest version
- tutu doctor: check network and sign-in
- tutu uninstall: uninstall (your tools are left alone)
- tutu node: install as a Tutu Compute Node
FAQ
No. The first run opens your browser, and you can continue as a guest without signing in; once signed in, the same computer stays signed in.
Not silently. When there's a new version, tutu mentions it in its status and updates when you run tutu update; it updates on its own only when it's below the minimum version.
No. Your installed copy is used; if it's too old, a new copy is installed alongside and yours stays as it is.
macOS (Apple silicon and Intel), Linux (x64 and ARM64), Windows (x64 and ARM64).
Run tutu uninstall: the program, sign-in credentials and logs are removed; your tools are left alone.
Related
Tutu CLI: every coding AI from one command