Book a consultation
Product tour

Every screen of Command Center, one chapter each.

Thirteen chapters: twelve figures and a table of keyboard shortcuts. Each figure is an illustration of the Windows app with sample data from fictional companies, so you can see how it works before you try it.

Request early access See pricing

Windows 10 and 11, x64. Uses your own Anthropic API key.

Up to sixteen sessions, side by side.

Each cell is a full Claude Code chat: the transcript, every tool call, questions with answer buttons and a footer with the model, context used and the cache countdown. Pick the layout that fits the work: 1, 2, 3, Focus, 4x2 or 8x2.

  • The sidebar groups sessions by status: Waiting for you, Working, History.
  • Tags such as a client or a repo filter the sidebar in one click.
  • The cache countdown shows how long a reply stays cheap, so you answer the right cell first.
+ New session Ctrl N 123Focus4x28x2 Next waiting Ctrl J Today$7.85 Running3 Waiting1
Search sessions Ctrl K
northwindhalcyontidewater+
Waiting for you1
Northwind invoice export2mUTC or customer time zone?
Working3
Ferrous Works API v23 agents
Tidewater docs sweep9 / 14
Ops: flaky checkout test12m
History1,418
Orbit release notesToday
Halcyon: image pipeline30 Oct
Northwind invoice exportnorthwind1
Add a CSV export of invoices to the billing page.
✓ Read billing/export.ts and 4 tests
✓ Wrote GET /invoices/export.csv
✓ 12 tests green
Asks you
Export dates in UTC or in the customer's time zone?
UTCCustomerAsk finance
Reply, or type / for skillsEnter
Opusctx 41%cache 3:42$2.10
Ferrous Works API v2coordinate2
Move the v1 routes to v2 without breaking the mobile app.
scout
done
worker
4 / 5
careful
2 / 4
The mobile app still calls /v1/me, so worker keeps a shim for one release.
Reply, or type / for skillsEnter
Opusctx 22%cache 0:48$4.80
Tidewater docs sweeptidewater3
Rewrite the 14 setup pages so each one has a working example.
✓ 9 of 14 pages rewritten
✓ Examples run on a clean folder
Writing install-on-windows.md
Reply, or type / for skillsEnter
Sonnetctx 54%cache 1:10$0.90
Fig. 1The three-column layout. One cell waits for an answer, two keep working. The footer of each cell shows model, context used, cache countdown and spend.

You hear it the moment an agent needs you.

When a session asks a question or reaches a checkpoint, Command Center plays a sound, raises a Windows notification and shows a toast inside the app. The cell turns amber and moves to Waiting for you.

  • Open jumps to the cell. Put in group places the session in a free group of the grid, or one that is not waiting on you.
  • Later keeps it in Waiting for you without another sound.
  • Ctrl J walks through every waiting session, oldest first.
Windows notification
Command Centernow
Halcyon Studio checkout needs you

Hide the coupon field until the customer taps "Add a code"?

OpenLater
Alert settings
SoundSoft chime, once per question
Windows notificationAlso when the app is minimized
In-app toastOpen, Put in group, Later
Inside the app
Halcyon Studio checkoutnow
Needs you: hide the coupon field until the customer taps "Add a code"?
OpenPut in group 2Later
Waiting for you1
Halcyon Studio checkoutnowHide the coupon field?
Northwind invoice export4mUTC or customer time zone?
Fig. 2One question, three signals: a Windows notification, an in-app toast and a new row in Waiting for you. The Windows notification is drawn in neutral greys; its look follows your system theme.

One session plans the job and runs the others.

Turn on Coordinate and the session becomes a coordinator. It writes a plan, starts child sessions, hands each one a task, reads their reports and tells you when the whole job is done. You can open any child and read what it did.

  • In a coordinated job, a command that sends to an audience, starts a paid generation or deploys stops at a checkpoint and waits for you.
  • The auditor checks the combined result before the coordinator reports back.
  • Coordinate is a switch on any session. Turn it off and the session works alone again.
Coordinator: Halcyon launchcoordinatehalcyon5
Ship the 2.0 launch: landing page, two emails and release notes. Ask me before anything sends.
Plan, 4 tasks. Designer builds the landing from the approved mockup. Writer drafts both emails and the notes. Engineer wires the signup form. Auditor checks all of it before I report.
designer
done
writer
3 / 4
engineer
2 / 5
auditor
queued
Checkpoint
The launch email is ready for 2,140 subscribers. Send it now?
ApproveChangeCancel
Opusctx 29%cache 2:05$3.10
Reports from children3
✓ designer: landing rebuilt, screenshots at 1440 and 390 match
✓ writer: email 1 and release notes drafted, email 2 in progress
✓ engineer: form posts to the staging list, 6 tests green
Next: auditor reads all three, then the coordinator reports to you.
Fig. 3A coordinator with three children and a queued auditor. The send waits at a checkpoint until you choose.

An auditor checks every deliverable first.

Sessions are instructed to hand finished work to an auditor agent. It reads the result, runs it and ranks what it finds as Blocker, Major or Minor. Any Blocker or Major is a FAIL and goes back with line numbers and screenshots. A PASS reaches you with its evidence.

See a full sample audit
  • Code, copy, design and data each have their own checks.
  • Nothing is called done without fresh evidence from a real run.
  • The auditor starts with a clean context, so it reads the work the way you would.

Re-audit: Northwind invoice export

PASS
Blocker
Resolved: export included invoices from other workspacesThe query now filters by workspace id. Reproduced the old case; it returns 0 foreign rows.
Minor
Resolved: column header said "Ammount"Fixed in billing/export.ts line 31.
Minor
Note: the CSV uses commas as separatorsFine for the current customers. Semicolons may suit European spreadsheet defaults later.
evidence: 14 tests, 1 real export of 312 invoices, 2 screenshotssent to you with the deliverable
Fig. 4A PASS after a re-audit. Every resolved finding says how it was checked; the Minor note is advice and does not block.

An Office of named specialist agents.

The Office is a roster of agents you define: a designer, an engineer, an analyst, a copywriter, a researcher, a CFO, a CIO. Each has a name, a role, the skills it loads and the person it reports to, grouped by department.

  • Talk to a member directly from the roster, in a new session.
  • Or let the coordinator pick members for each task of a job.
  • A department head plans and reviews the work of its members.
Engineering
CIO
Rhea plans and reviews
lead
FS
Tomas full-stack engineer
working
QA
Lio test engineer
idle
DB
Sana data engineer
idle
Marketing
CMO
Odile plans and reviews
lead
DS
Wren designer
working
CW
Pax copywriter
working
RS
Imre researcher
idle
Finance and data
CFO
Marguerite reads spend, recommends
lead
AN
Kofi analyst
idle
Talk to Kofi
+ Add a member
Fig. 5An Office with three departments. Leads plan and review; members show whether they are working on a task right now. Names are examples you replace with your own.

Every subagent, its status and its progress.

Sessions start subagents for scouting, careful edits or tests. The agents tree lists every one a session spawned, nested under the agent that started it, with a progress bar and its last action. Click a row to read what it is doing.

  • Status dots match the sidebar: working, done, waiting for you.
  • Progress counts the steps the agent planned, so a bar never moves by guesswork.
  • Stop one agent without stopping the session.
Agents: Ferrous Works API v26 agents
scout
done
route map
done
worker
4 / 5
tests v2
3 / 5
careful
2 / 4
auditor
queued
worker4 of 5 steps
Task from the coordinator
Port the 11 user routes to /v2 and keep /v1/me as a shim for one release.
✓ 11 routes ported
✓ Shim added for /v1/me
✓ 38 tests green
Updating the OpenAPI file
Open transcriptStop agent
Fig. 6The agents tree for one session. Nested rows are agents started by another agent; the selected row opens its task and its last actions.

Review pages you can mark up.

When an agent produces a plan, a report or a mockup, it opens as a page inside a cell. Click any element to leave a note on it. When you press Send, the notes go back to the session with the element each one points at.

  • A new page opens in a free cell, so you see it without switching windows.
  • Notes keep their place on the page, numbered in the order you wrote them.
  • The agent replies with a new version of the page; older versions stay in History.
Review: Q4 launch plan, version 2halcyon4
Review page3 notes
Notes on this page3
1
TitleSay "2.0" in the title, people search for it.
2
Budget boxMove the ads budget to week 2, after the landing is live.
3
Risks tableAdd the app store review delay as a risk.
Note on this pageSend 3
Fig. 7A plan opened as a review page with three notes. The pins mark the elements; Send returns all three to the session that wrote the plan.

Two sessions, one repo, no overwritten files.

When you open a second session in a folder that already has one, Command Center gives it its own git worktree, so each session edits its own copy of the files. If a session is about to write a file that another live session wrote in the last 30 minutes, you are asked before it happens.

  • Worktrees are created and named for you; the cell header shows which one a session uses.
  • The collision question names the file, the other session and how long ago it wrote the file.
  • Answer Move to a worktree, Proceed or Cancel.

New session

What do you needSweep the API docs for the v2 routes
FolderC:\work\ferrous-api
1 session open
Isolated copy (worktree)ferrous-api, worktree 2, branch docs-sweep
Tagsferrous, docs
edit
CancelStart Enter

Collision: api/routes.ts

Also edited by Ferrous Works API v2, 6 minutes ago.

Edit api/routes.ts
Move to a worktreeProceedCancel
Fig. 8Left: a second session in the same folder gets worktree 2. Right: the question that appears when a session is about to write a file another live session wrote in the last 30 minutes.

See what every key spends.

Usage shows what your API keys spent today, per session and over the last 14 days. Each Anthropic account you add shows what its key has spent. To bill a session to another key, switch it to another account and the session keeps its history.

  • Spend is read from your own API usage. Command Center adds nothing to it.
  • The cache column tells you which session to answer first to avoid paying for context again.
  • Several accounts on Pro and above.
Usage, last 14 days$168.20
SessionTodayCache
Ferrous Works API v2$4.800:48
Northwind invoice export$2.103:42
Tidewater docs sweep$0.901:10
Other 4$3.60closed
AccountsSettings, Accounts
Account A, work key$7.20 today, $96.40 in 14 days
Account B, team key$2.90 today, $52.10 in 14 days
Account C, personal$1.30 today, $19.70 in 14 days

Move Ferrous Works API v2 to Account B?

The session keeps its transcript, agents and worktree. New requests use Account B from the next message.

CancelSwitch
Fig. 9Usage and Accounts side by side: spend per session, per day and per account. One session moves to the team key, Account B.

Answer from your phone, on your own network.

Pair a phone over Tailscale, your private network. Questions reach the phone with the same answer buttons. Tap one and the session continues on the PC. The app listens on your Tailscale address only, so nothing is exposed to the public internet.

  1. Turn on Remote in Settings. The app shows a pairing code and your Tailscale address.
  2. Open the address on your phone while it is on the same Tailscale network.
  3. Enter the code once. The phone is now a paired device; remove it from Settings at any time.
07:12Tailscale
Command Center1 waiting
Ferrous Works API v2
Both fixes are done and passed the audit.
Question
Bump the version to 2.4.1 or 2.5.0?
2.4.12.5.0
Tidewater docs sweep
12 of 14 pages, writing faq.md
Orbit release notes
Audit PASS, review page ready
SessionsWaitingUsage
Fig. 10The phone remote at 07:12. A session waits on a question; one tap answers it on the PC.

Shared company sessions, with secrets removed.

On the Team plan, sessions you run for a company you share are uploaded to the Hub automatically. Before upload, keys, tokens and passwords in the transcript are replaced on your PC. Your teammates' sessions for that company arrive in your History with their names.

  • Redaction runs on your PC, before upload. The Hub never sees the original transcript.
  • Token-shaped strings, passwords in URLs and labelled secrets are replaced with [redacted].
  • Which sessions are shared follows the company, so there is nothing to press.
History: Halcyon Studiofrom the Team Hub
Checkout v3 rolloutTATeo Alvarez, updated 20 minutes ago
Image pipeline on GPUJRJun Ruiz, updated 2 hours ago
Q4 launch planSOSara Okoye, updated yesterday
Support macros rewriteMCMia Chen, updated 30 Oct
Fig. 11Teammates' sessions for Halcyon Studio, downloaded from the Team Hub and listed in History with the name of the person who ran them.

Start at the desk, find it on the laptop. Planned

Planned for Pro and above: settings and session history will move between two of your machines, so a session you finished at the desk will be in History on the laptop, with its transcript and reports.

  • Planned to travel: settings, layouts, tags, the Office roster and session history.
  • API keys will stay on each PC, where they are encrypted for that Windows account.
  • Running sessions will stay on the PC that runs them.
Desk PCWindows 11, this PC1,418 sessions in History4 running
⇄
planned
LaptopWindows 111,418 sessions in History0 running
Settings and layoutsplanned
Tags and Office rosterplanned
Session history and reportsplanned
Anthropic API keysstays on each PC
Fig. 12Planned: two PCs, one history. Keys will stay on each machine.

Keyboard shortcuts.

The shortcuts that matter when sixteen sessions are open. They work from anywhere in the window.

KeysAction
Ctrl JJump to the next session waiting for you, oldest first
Ctrl KSearch every session by title, tag or text
Ctrl NStart a new session
Ctrl 1 to Ctrl 8Focus cell 1 to 8 of the grid
EnterSend your reply in the focused cell
Shift EnterNew line in a reply
/Open the skills list in the reply box

See it with your own sessions.

Command Center is in early access. Request access and we will email you when you can download it, add your Anthropic API key and open your first grid. Solo, Pro and Team will start with a 14-day free trial.

Request early access See pricing