Agents do the work.You steer.

Run a team of Claude Code agents on your own computer. Switchboard keeps them on track, takes the busywork off your desk and brings you only the decisions worth your time.

Download for Windows

Free for personal use

HomeSearch sessions, changes, pages…/7.7 GB5.8 GB18%42%
Saturday afternoon · 3 projects
6 agents working, 4 things waiting on youOpen Needs you
Needs you42 approvals · 1 question · 1 promote
Sessions6working · 3 idle
Changes in progress73 finishing · 4 building
Ready to promote36 commits on dev
Plan usage18%5-hour · weekly 42%
Changes22 openBoard
Draft 4Ready 5In progress 7Built 6Done 107
In progress
Questions say why they came up
ask-contextTesting13/13
Builds end themselves when stuck
build-stopBuilding5/37
Sign in with your own Claude account
login-through-claudeBuilding14/14
Installers and updates
desktop-releaseTesting19/30
Repository hygiene before distribution
repo-hygieneBuilding4/4
Builds2 runningAll builds
Android kiosk build
kiosk-admin-dashboard4 min
Preview dev
dev · 44f53c31 min
Deployed main
main · 7f2d0b12 h
Worth a look
3 changes ready to promote
login-through-claude is ready to finish
Disk space: 9% free

Dozens of changes at once.

Each has its own agent and its own branch. The board shows where every one stands, so one person can run all of it.

SwitchboardChanges 129 changes · 14 worktrees Supervisor is handling 4 items
Draft4
reopen-changesReopen a change after it is doneproposaldesignspecstasks
design-syncKeep the design and the app in stepproposaldesignspecstasks
phone-tasks-overlapTask cards on a phoneproposaldesignspecstasks
stray-ref-plusStray branches cleaned upproposaldesignspecstasks
Ready5
multi-userSeveral people, each signing in as themselves0/39Review
desktop-windows-proofSwitchboard proven on clean Windows computers0/17Review
person-tasksTasks for the person0/22Review
landing-decisionsA new landing page0/11Review
roadmapA roadmap: ideas, goals and the order of changes0/23Changes asked
In progress7
ask-contextTestingQuestions say why they came up13/13 Finish
build-stopBuildingBuilds end themselves when stuck5/37
login-through-claudeBuildingSign in with your own Claude account14/14 Finish
desktop-releaseTestingInstallers and updates19/30
repo-hygieneBuildingRepository hygiene before distribution4/4 Finish
Built6
bundled-claudeSwitchboard has Claude Code preinstalled36/36on dev · 4442065
answered-asks-leaveAnswered questions leave Needs you11/11on dev · 718c606
hotfix-size-limitA hotfix touches at most three files17/17on dev · e5c211e
chat-button-rowOpen chat as a labelled button12/12on dev · 630685e
change-tabs-fitChange tabs fit the page9/9on dev · 422e5a4
Done107
desktop-shellA desktop app with Switchboard inside28832053live
server-serviceSwitchboard as a background service3c08482flive
finished-session-keptA finished change keeps its session until Promote7b596405live
promote-resolves-conflictsPromote resolves its conflicts before your click973a5c67live
asks-survive-handoverA change's open questions survive a hand-over3c3eac9clive

Only what needs you, in one place.

Every question, approval and release lands in one queue with one clear action. Clear it from your desk or your phone, then get on with your day.

Needs you4newest first
Review before building2 min
Retry failed exports
export-retry
Question9 min
Retry failed exports
export-retry
Approval14 min
Kiosk admin dashboard
kiosk-admin-dashboard
Promote1 h
3 changes ready for main
dev · 44f53c3
6 agents working · supervisor handling 2
Review before buildingwaiting 2 min1 of 4
Retry failed exports
export-retry Summary from the proposal

Exports fail about twice a day when the storage API times out. Retry three times over fifteen minutes, show each attempt, then ask.

Plan, then code · 3 steps · 6 tasks
Approve and build BAsk for changes

Approve the plan, not the code.

You set the goal. The agent writes a proposal. You get a summary. You can steer and override. Approve to start building.

export-retryNew changeSession · waiting for a goal
you
You
Exports fail about twice a day when the storage API times out. Retry them, and only ask me when it keeps failing.
Reading export/retry.ts and the export page
Exports fail when the storage API times out, and each one waits for someone to notice. A retry needs a wait between tries, and how long is a choice.
Asked the supervisor: exponential backoff or a fixed 30 s wait?
Supervisor answered
Exponential, capped at five minutes. Exports take minutes to recover; backing off gives the API that time.
Writing proposal.md and design.md
Writing 2 specs and tasks.md · 6 steps, 15 tasks
Ready for your review. The proposal and the plan are on your board. Building starts when you approve.
Message the session…
Review before buildingwaiting 2 min1 of 4
Retry failed exports
export-retry Summary from the proposal · 2 min ago
Why

Exports fail about twice a day when the storage API times out, and each one waits for someone to notice.

What changes
  • A failed export is retried three times over fifteen minutes
  • The export page shows each attempt and its reason
  • After the third failure it asks you
Plan, then code6 steps · 15 tasks · 3 decisions
Approve and build BOpen change VAsk for changes ROpen chat
SwitchboardChangesexport-retry Ready · Review before building
Retry failed exports
export-retrychange/export-retry.claude/worktrees/export-retry
The agent wrote the proposal and the plan, then stopped. Building starts when you approve.Approve and buildAsk for changes
Proposal Design Specs2 Tasks0/15 Decisions3 Follow-ups1 SummaryRaw
Summary compiled by the session from proposal.md · 2 min ago
Why

Exports fail about twice a day when the storage API times out, and each one waits for someone to notice.

What changes
  • A failed export is retried three times over fifteen minutes, backing off between tries
  • The export page shows each attempt and its reason
  • After the third failure it asks you
Follow-ups · 1

Retry other background jobs the same way. Once exports hold up, the same wait and attempts list fit imports and report runs.

A supervisor answers the small questions. You see every one.

It handles the routine; security, money and deleting work stay yours, and you can overrule any answer.

export-retryRetry failed exportsSession · drafting
Reading export/retry.ts
Exports fail when the storage API times out. A retry needs a wait between tries, and how long is a choice.
Checking how long the API takes to recover
Questionto the supervisor
Exponential backoff or a fixed 30 s wait?
Waiting for the supervisor · the session carries on with the rest
Supervisor answered
Exponential, capped at five minutes. Exports take minutes to recover; backing off gives the API that time.
Carrying on: exponential backoff, capped at five minutes.
Reading db/exports.sql
Each export is one row. The attempts could live on it or in a table of their own.
Questionto the supervisor
Store the attempts in the export row or a new table?
Waiting for the supervisor · the session carries on with the rest
Supervisor answered
In the export row: three attempts at most, and the page reads one record.
Carrying on: three attempt columns on the export row.
Reading the design notes for the export page
The page shows one export at a time; the attempts need a place on it.
Questionto the supervisor
Where should the attempts show?
Waiting for the supervisor · the session carries on with the rest
Supervisor answered
On the export page, under the export. The list is drawn from the tokens, so it is flagged for your review.
Carrying on; the list is flagged for your review.
Message the session…
Supervisor decisionsexport-retry0 of 3 decided
Exponential backoff or a fixed 30 s wait?
Store the attempts in the export row or a new table?
Where should the attempts show?

Questions arrive in plain words.

When something is yours to decide, the card says why it came up, what each choice means for you, and what the agent recommends.

Questionwaiting 9 minexport-retry
Should failed exports be retried on their own, or wait for you?
Retry on their own Recommended
Three tries over fifteen minutes, then it asks you.
Wait for me
Every failure becomes a card here; each retry is your call.
What it changes for you: fewer cards; a stuck export may take up to fifteen minutes before you hear.
Why it came upWriting the retry, I found exports fail about twice a day and each one waits for someone to notice. Retrying on its own saves you a card each time; waiting for you keeps every failure in your hands.
SendSkip · the agent decides S

Ship what you pick. It's already finished.

A change reaches dev only when it is finished and its checks pass. Promote takes dev to main: tick the changes to go live, look at dev's preview, and Switchboard merges them into main with a plain merge commit, then deploys.

Promotewaiting 1 h
Promote 3 changes to main
dev 44f53c3mainmerge commit, then deploy
What goes live3 of 3 changes · 6 commits
export-retryRetry failed exports 6 of 6 tasks
plan-limitsPlan limits read from the usage endpoint 4 of 4 tasks
narrow-screensSidebar and tables reflow under 900px 7 of 7 tasks
Previewdev was previewed at 44f53c3Open dev's preview
MergeA plain merge commit onto main. If main has moved, you see it before anything deploys.
Promote… PPreview dev VLater

Trunk-based development, enforced

dev main change/export-retry finished · lands on dev change/plan-limits Promote · your click

Every change on its own branch, on your computer. Finished work lands on dev. Promote merges dev into main.

Free for personal use.

Personal Free

For personal use only, on your own Windows computer. Download it today. Your repository stays with you.

Teams Coming soon

Several people on one Switchboard, each signing in with their own Claude account. Sign up to be notified.

Hosted Coming soon

We run it for you, on our computers. Opening later. Sign up below to be notified.

Teams and Hosted

Both are on their way. Leave your email and tick what you want to hear about; we'll write once for each.

We keep only your email and what you ticked. Privacy