Cluster Build

A coding agent
in your terminal.

Describe the change. Cluster Build reads your code, edits the files, runs the tests, and shows you every step — from one command.

macOS and Linux · then cluster login

Read the QuickstartDocumentation
❯ cluster Cluster Buildgpt-5.6 with medium effort · Cluster Max escape interrupt · ctrl+c/ctrl+d clear/exit · / commands · ! bash · ? more Tip: Use /plan to see a plan before anything touches your project. [Context] AGENTS.md
›
Build anything
gpt-5.6 · ~/code/api
One sign-in
Use your Cluster account. There are no API keys to manage.
Any model
Claude, GPT, Kimi, DeepSeek, or a local Ollama model, picked per session.
Your machine
It runs in your terminal, on your files, with your permissions.

01

Plan mode

Get the plan before anything touches your project.

  • Shift+Tab or /plan blocks every edit and command for the session
  • The assistant reads, searches, and asks structured questions instead
  • Implement the plan in place, revise it, or start from a fresh context
› /planPlan mode on — edits and commands are blocked. › move session storage from Redis to Postgres Read    src/sessions/store.tsGrepped SessionStore src/            11 matchesAsked   Keep Redis as a read-through cache?   No • Proposed Plan  1. Add a sessions table and a migration  2. Implement PgSessionStore behind the SessionStore interface  3. Swap the binding in src/app.ts, delete the Redis store  4. Port the store tests, add one for expiry Implement this plan?→ Yes, implement this plan  Revise this plan  Yes, clear context and implement  No, stay in Plan mode
›Build anything
gpt-5.6 · plan · ~/code/api

02

Cloud planning and review

Hand the big jobs to a fleet of agents and keep working.

  • /megaplan clones your repos on a remote machine and streams a plan back
  • /megareview runs specialist reviewers in parallel and cross-checks their findings
  • Both run in the background and deliver results into the conversation on their own
› /megareview Reviewing feature/pg-sessions against main  ·  6 files, +312 −188Running in the cloud — I’ll post the findings here when it’s done. › meanwhile, add the migration rollbackEdited  migrations/0007_sessions.sql             +9 ✓ Review finished  ·  5 agents, 3 findings confirmed  high   expiry uses server time, not the session’s created_at  medium PgSessionStore.get swallows connection errors  low    missing index on sessions(expires_at)Posted to acme/api#482
›Build anything
gpt-5.6 · ~/code/api

03

Remote control

Walk away mid-build and pick the session up from your phone.

  • /remote publishes the session to the Cluster mobile app and cluster.app/build
  • Scan the QR code in the terminal to open it on your phone
  • Work still runs on your machine; the remote sends prompts and streams output back
› /remote
Remote Control

This session is available in the Cluster mobile app and at

https://cluster.app/build/sesn_a22dfb71…

Disconnect this session

→ Hide QR code

Continue

Enter to select · Esc to continue

›Build anything
kimi-k3 · ~/code/api/rc

04

Local agents

Split the work across child agents in the same workspace.

  • Up to three children run at once, each with its own directory, model, or effort
  • They report a bounded result back and never see your transcript
  • Separate terminal sessions can message each other directly
› auth, billing, and search all log differently — unify them on pino Spawned agent/auth      services/auth      runningSpawned agent/billing   services/billing   runningSpawned agent/search    services/search    running agents: 3 running, 0 completed agent/search   done  4 files, replaced console.* with a shared loggeragent/auth     done  7 files, kept the request-id child loggeragent/billing  done  3 files, one test updatedRan     bun test                              212 passed
›Build anything
gpt-5.6 · ~/code/monorepo

05

Memory

It remembers how you like things done.

  • /remember pins a fact for this project or for every project
  • Finished sessions are summarized into inspectable Markdown under ~/.cluster
  • Turn learning off, or memory off entirely, whenever you want
› /remember project migrations are hand-written SQL, never generatedPinned to project memory. — three days later — › add a last_seen_at column to users Recalled migrations are hand-written SQL, never generatedListed   migrations/Wrote    migrations/0008_users_last_seen_at.sql   +4Edited   src/db/schema.ts                        +1
›Build anything
gpt-5.6 · ~/code/api

Try it in your terminal

One command to install. Works in any repository, any language.

Everything you need to ship

One tool for the whole loop — plan, build, test, review, and pick it up again tomorrow.

  • Plan mode

    A read-only pass that ends in a plan you approve

  • Local agents

    Up to three child agents working in parallel

  • Cloud review

    A fleet of reviewers on your diff, posted to the PR

  • Cloud planning

    Plan across repos you don’t have checked out

  • Remote control

    Follow and reply to a session from your phone

  • Memory

    Durable facts across sessions, in plain Markdown

  • Any model

    Claude, GPT, Kimi, DeepSeek, or your own Ollama

  • Reasoning effort

    Dial thinking from minimal to max per run

  • Code search

    ripgrep-backed search across the whole tree

  • File edits

    Patches and rewrites, shown as diffs

  • Shell

    Run commands, keep long processes in the background

  • Shell mode

    Start with ! to run a command yourself

  • Headless exec

    cluster exec for scripts, pipes, and CI

  • Sessions

    Resume any conversation, from any directory

  • Skills and commands

    Your own slash commands under ~/.cluster

  • MCP servers

    Connect tools and manage them with /mcp

  • Images

    Hand it screenshots and mockups as context

  • Computer use

    Opt-in desktop control on macOS and GNOME

  • Workspace trust

    Nothing runs until you trust the directory

  • Themes

    Syntax colors and light or dark appearance

  • Self-updating

    cluster update keeps the binary current

Bring Cluster to your terminal

Install, sign in with your Cluster account, and start on your first task in a couple of minutes.

Read the QuickstartGet a Cluster account