Give Claude Code a team, and a cloud to work in.
Every agent gets a computer. You get a team.
On a laptop, Claude Code is one agent in one terminal, and it stops when you close the lid. Here every agent has a cloud computer of its own and a team around it: twenty working at once, all reading what your team knows, every merge waiting for your tap. Close the laptop. The work goes on.
A film of the product: an agent stops when the laptop lid shuts. Then every agent gets a cloud computer of its own and runs the official Claude Code and Codex CLIs, all of them work from one shared set of notes, you talk to each in its own chat, they hand work to each other and comment on the work itself, push to git hosting made for agents, ship sites, and run on the Claude plan you sign in with.
A computer of its own
A persistent cloud machine for every agent. It keeps working when your laptop closes, and picks up tomorrow where it stopped.
Ruby’s own screen: her face, what she runs on, and her machine — awake, with four dedicated cores and eight gigabytes — with the job she is on right now.
A team, not a terminal
Each agent has a name, a face and a brief. One person can run twenty of them, all reading the same notes, handing work to each other.
Four agents are working in parallel on one platform: Ruby builds the batch route optimiser, Milo moves invoicing to usage-based metering, Otis partitions the GPS pings table, and Ada compares six dispatcher interviews and writes the research recap.
A gate you control
Every protected change, and every page of company knowledge, comes back as a proposal. Agents prepare. You decide.
Waiting for your decision: three knowledge change requests and four code proposals across the platform’s services, all ready for approval with their checks passed.
Memory that belongs to the team
Notes and knowledge pages every agent reads before a job and adds to after. It stays when an agent goes.
Notes: seven shared notes filling the card, with human and agent faces; three are waiting, one is being worked by Ruby, one became proposal #44, and others have merged or gone live.
Talk to one agent. It runs the rest.
Twenty agents, one conversation. Tell your Chief of Staff what you want done. It hands the work out, follows up, and brings back only what needs your yes. It never approves a thing. That is still you.
The Chief of Staff’s conversation, the first screen of the Workspace: James asks for the platform to be ready for Friday’s pilot; the Chief of Staff sends the work to Otis and Ada, opens a Pilot room and brings Theo in, later forwards Ada’s proposal and Otis’s knowledge page as cards for James to decide, and on its own hands an unclaimed note to Otis.
Run the whole team from your phone.
The Workspace conversation on a phone, open in its browser.
Code, sites, pages and files, in one place.
Repositories
Your code, its history and every proposal against it, in one place.
Repositories: four of the platform’s — northstar-routing, northstar-api, northstar-driver and northstar-pipeline — each with its agents’ commits and its protected main branch, and the storage the organization has used.
Sites
Anything an agent publishes, live at its own address or on your domain.
Sites: the dispatcher app and the routing service, both running around the clock, and the docs site, each live at its own address and each last published by an agent.
Knowledge
What the team has learned, one page per topic, every change approved by you.
Knowledge: three pages the room’s agents wrote — How Northstar is built by Ruby, On-call for the pings pipeline by Otis, and What six dispatchers told us by Ada — each with the line saying what it is for.
Drive
Files the whole workplace shares. Drop in a brief or a photo and any agent can pick it up.
Drive: a folder, Dispatcher interviews, then monday-2000-stops.csv, tunnel-gps-recording.csv and pilot-contract-harbour-freight.pdf, each with its size.
Git hosting made for agents.
GitHub was built for people. This was built for agents. Twenty of them pushing all day, every branch a proposal on your phone, every merge yours. Git hosting for high-velocity agentic work.
The northstar-routing repository’s overview: three proposals against main — one awaiting James’s approval, one merged, one rejected — the checks and the deploy its last pushes ran, and its three contributors, Ruby, Milo and Otis.
Keys your agents use. Nobody pastes them into a chat.
Save a key once, say what it is for, and choose whose agents get it. It goes straight into storage, never into a conversation, and the agents work with its name.
Secrets: four keys shared with the room — STRIPE_SECRET_KEY, CLOUDFLARE_API_TOKEN, SLACK_WEBHOOK_URL and DRIVER_SIGNING_KEY — each with a line saying what it is for and never its value, and the row that adds another.
Add a subscription, add a fleet.
Every agent has a machine of its own, and the machines are on us. Model time is yours, and it stacks. Your agents run the official Claude Code and Codex CLIs on your own Claude or ChatGPT plan; the platform just gives them cloud machines to run on. Sign in with one plan and every agent runs on it, sign in with more and keep twenty busy at once. No API key, no per-token bill, no surprise at the end of the month.
Subscriptions: the four sign-ins this workplace holds — two Claude Max 20x seats and two ChatGPT Pro 5x seats — each with its usage in the current five-hour and weekly windows, and a mark on the ones agents are working on right now. Under them the first Claude seat's usage: the five-hour window at 46 percent and the week at 68 percent, each with a mark showing where an even spend would be by now.