manage your coding agents like a team. not a terminal.
boum is a calm macOS layer over your own claude code and codex. file work as tickets, walk away, and come back to a result — or the one decision that needs you.
apple silicon · brings your own claude code & codex
early alpha — for hobby & side projects, not production work
slate
boum desktop · 7 openneeds you · 2
in progress · 3
done
the model
you manage the work, not the agent.
the interface is silent because the power is what’s loud. boum gives ai coding the structure you already use for engineers — and surfaces only the human moments.
tickets, not transcripts
organisations, projects, epics, stories, tickets — with acceptance criteria and history. you manage the work, never a wall of scrollback.
your agents, your keys
runs your own claude code and codex, with your auth, on your repos.
your CLIs · your keys
needs-you, not notifications
a question, a decision, a review — and silence the rest of the time.
every result is reviewable
work lands as a versioned change with its acceptance criteria checked off — not a “done” you have to take on faith.
- toggle persists per project
- claude code path spawns
- codex path spawns
the one decision, brought to you.
most of the work needs no one. when something genuinely needs a human — an ambiguous spec, a tradeoff, a review — boum opens exactly that, with the context already loaded. you decide in a sentence and it keeps going.
- questions, decisions, and reviews — never raw logs
- acceptance criteria tracked, so “done” means done
- quiet by default — no badges, no nagging, no pings
wire the dual-backend toggle
let a project run on claude code or codex; persist the choice and restore it on relaunch.
acceptance criteria
- toggle persists per project
- claude code path spawns
- codex path spawns
- state restored on relaunch
1 decision waiting — default backend for new projects?
how it works
whisper a ticket. the work explodes elsewhere.
file a ticket
write what you want and point it at a repo. add acceptance criteria, or don’t.
the agent works
claude code or codex runs on your machine, against your code, with your keys.
you review what matters
boum brings you the questions and the diffs. the rest just ships.
“i don’t watch my devs write every line. why would i watch claude?”— the whole idea, in one line
questions
the honest answers.
do i need my own claude code or codex?
yes. boum runs your own CLIs with your own auth — it never sits between you and the model, and never sees your keys. you bring the agents; boum gives them structure.
is it on the mac app store?
no — boum is a notarized direct download. the app store sandbox would block boum from spawning your claude code / codex and reading your repos, which is the whole point. you download it, gatekeeper trusts it, it auto-updates.
what does it cost?
free during the open alpha — and early users stay free. a paid tier comes later for new users. it’s a focused tool for people who manage their own agents, not a platform.
is it production-ready?
no — boum is an early alpha. expect rough edges and the occasional breaking change. use it on hobby work and side projects, not production-critical repos. it improves quickly, and early users help shape it.
where does my code go?
nowhere. boum runs locally on your machine, against your repos, driving your own agents. there is no boum backend in the loop.
can i use claude code and codex together?
yes. choose a backend per project and switch anytime — the same tickets, either engine.
which macs are supported?
apple silicon, on a recent macOS. that’s the alpha target for now.
stop watching the terminal.
download for macOSfree during alpha · apple silicon
early alpha — for hobby & side projects, not production work