CloudThinker CLI
Run cloudthinker and ask Frontier Investigation Agents in plain language. The CLI checks its setup, shows progress and returns the result. For scripts, chat -p prints only the answer.
chat -p prints only the answer on stdout. Progress goes to stderr, so it fits in a pipeline.
One line to install, one command to sign in. Then say what you need.
Install
The installer puts cloudthinker in ~/.local/bin and adds it to your PATH. Open a new shell after it finishes.$ curl -fsSL https://cloudthinker.io/install.sh | sh
Sign in
Your browser opens. Approve the device and pick the workspace. On a machine with no browser, add --device-auth.$ cloudthinker login
Run it in a project folder
The agent edits files and runs commands in that folder. The model and your Connections stay in CloudThinker.$ cloudthinker
$ curl -fsSL https://cloudthinker.io/install.sh | shUse it by hand, or wire it into scripts, cron jobs, and CI.
Ask in plain language
Run cloudthinker with no arguments and say what you need. It configures and repairs what it can, then returns the result.$ cloudthinker
Pipe anything in
chat -p prints only the answer on stdout. Progress goes to stderr, so it fits in a pipeline.$ kubectl logs deploy/api --tail 200 | cloudthinker chat -p "Why does this crash?"
One result for scripts
Add --json to get one machine-readable result you can parse.$ cloudthinker chat -p "Draft the rollout plan" --json
macOS on Apple Silicon and Intel, and Linux on x86_64 and arm64. Windows has no agent bundle yet, so there is no installer for it.
The model and your workspace Connections stay in CloudThinker. When you run cloudthinker in a project folder, the agent edits files and runs shell commands in that folder on your machine.
Use chat -p with your prompt. stdout carries only the final answer and progress goes to stderr. Add --json for one machine-readable result.
Run cloudthinker login --device-auth and type the short code in a browser on another device. Over SSH, login picks this mode for you.
Run cloudthinker update.
The same binary runs a self-hosted sandbox. Chats in the browser, on a laptop or a phone, can then work in that folder.