Quickstart

Everything you need to go from zero to running AI DevBoxes on your own hardware.

1. Install the CLI

npm install -g @clustercode/cli
clustercode --version

Requires Node.js 22+. See Install CLI for details.

2. Log in

clustercode login

This opens your browser for a secure OAuth sign-in with your ClusterCode account.

3. Start a worker

clustercode worker

On first run, the CLI walks you through tenant selection and then starts the worker. The worker connects outbound to the orchestrator — no inbound ports, no firewall rules.

Or run the guided wizard that handles everything (login, tenant selection, runtime checks):

clustercode onboard

4. Sign your agents in on that worker

onboard prepares the machine — it does not sign your agents in. Do this once per worker, from the dashboard: open the worker’s page and click Sign-in agents.

Agent sign-in lets the agent think; service access tokens let it reach your code. Without both, your first DevBox comes up fine and the first agent command fails on auth. See Agent sign-in.

5. Launch your first DevBox

1. Open the dashboard at your orchestrator URL
2. Paste a GitHub issue link into the launch modal
3. Pick a worker and click Launch

Within 30 seconds the DevBox is running and the web terminal is live, with your repo cloned and the ticket context in place.

Now start the agent. Open the live terminal and run claude. The DevBox is the workspace; you (or a Run) drive the agent inside it.

6. Or let ClusterCode drive it

Don’t want to drive the terminal yourself? Instead of launching a DevBox, start a Run: paste the same issue URL, write “implement this and open a PR,” and the coordinator launches the DevBox and runs the agent for you. See Run an agent on demand.

What’s next?

• Run an agent on demand — hand a ticket over and get a PR back
• Launch from a ticket — full walkthrough of the hands-on flow
• Workers concept — understand self-hosted vs managed
• CLI reference — all available commands