Conduct a swarm of coding agents.
Claws turns VS Code's terminal panel into an orchestration layer. One MCP server. Parallel Claude sessions. You watch it happen live.
The single-agent ceiling.
One developer. One thread. One context window — paid for three times. As soon as the work outgrows a single context, you're back to opening three terminals and reconciling by hand.
One command. Many agents.
Dispatch
/claws-do classifies the work — shell, worker, fleet, wave, titan, or legion — then spawns visible terminals.
The bus
Every agent is a peer on a local pub/sub bus. worker.*.heartbeat, system.worker.completed — you subscribe, you don't poll.
The hierarchy
Six worker classes: shell → worker → fleet → lead → titan → legion. Higher classes coordinate; lower classes execute.
Memory is the product.
Every session writes structured memory. Incidents become draft lessons; promotions ship to every future session at boot. The corpus compounds — and it's the moat.
Watch the terminals work.
No chat window. Named workers in glass terminals, live in your VS Code panel.
Hands local. Brain in the cloud.
Free, local. Terminals, pty capture, the bus.
The moat. Classification, mission compile, memory recall. Zero LLM calls server-side.
Auth + Stripe. Free / Pro / Team / Enterprise.
You bring your own LLM — ~94% of every dollar is margin you're not paying for.
We ship in public.
“I stopped opening five terminals by hand. One mission, the fleet fans out, and I watch every agent in the panel.”
“The bus is the unlock — I subscribe to completions instead of babysitting. It feels like conducting, not micromanaging.”
Recent changelog
- v0.8.6—pricing anchor
- v0.8.5—capacity governor
- v0.8.4—CU-DNA