boum reads the session files claude code and codex already write and gives every one of them a live pane — its conversation as it is written, what it is doing, and what it needs from you. six side by side, each a keystroke away. no setup, no wrappers, nothing in the loop.
free during alpha · v0.0.21 · apple silicon & windows
early alpha — for hobby & side projects, not production work
the boum observatory demo: each drop of glass is a project running Claude Code. drops in the air are working; drops resting on the glass are finished or waiting. click a drop to open its session as a conversation — read it, answer its question with the numbered options, or type an instruction; speaking to a resting session resumes it.
the calm view · every session on this machine
output tok/s · stacked by project · last 3 min
7 projects · 9 sessions · +445 −201 uncommitted
edit · parser.ts2m
Read the whole module first. The public surface is four functions; everything else is private and free to move.
›Read · parser.ts
›Grep · callers of tokenize()
Refactor the parser — keep the public API exactly as it is.
Starting with the hot loop. The tokenizer allocates on every call, which is the real cost here.
›Edit · parser.ts
›Bash · run the unit tests
waiting on you4m
Draft the pricing page. Three tiers, no annual toggle.
›Read · pricing.tsx
The current page opens on the enterprise tier, which is the one almost nobody picks.
›Edit · pricing.tsx
Drafted. One decision I should not make for you — it changes who the page is written for.
Lead the pricing page with the studio plan, or the solo plan?
at rest11m
Two devices edit the same trip offline. What wins?
›Read · replay.ts
Last-write-wins loses edits people can see. I used a per-field merge and kept the conflict for the one case it cannot resolve.
›Edit · replay.ts
›Bash · replay the offline fixtures
Both devices converge now, and the one real conflict surfaces instead of being silently overwritten.
held at a prompt38m
Import the 2019 exports, skip anything already in the table.
›Read · seed.sql
Nine thousand rows, and about four hundred already exist. Matching on brew date plus name rather than id.
›Edit · seed.sql
›Bash · psql < seed.sql
likely a permission prompt — Bash · psql < seed.sql
bash · build1m
The first load is 340kb. Find the weight.
›Bash · analyze the bundle
The date library is 41% of the bundle on its own.
›Edit · format.ts
✗Bash · typecheck — 2 errors
›Edit · format.ts
at rest2h
›Read · digest.ts
The job is pinned to UTC, so half the readers get it the day before.
Send it at 7, not midnight.
Moved, and the timezone now follows the reader rather than the server.
›Edit · digest.ts
›Bash · run the scheduler tests
the wall
every session gets its own pane, and the words arrive as they are written — not a summary, not a status light. the panes never re-sort, so the wall is something you can aim at from memory: ⌘2 to move, then just type. no click, no hunting for the right window. it is the one thing a wall of terminals gets right, without the part where you cannot see any of them.
when a session stops to ask, its pane goes amber and the strip above says how many are waiting. so does a session stalled at a permission prompt — the one thing a transcript never records, and the reason a terminal can sit blocked for forty minutes without telling anyone. answer and boum resumes that session with your own CLI.
atelier · waiting 4 min
lead the pricing page with the studio plan, or the solo plan?
your words, the agent’s prose set as prose, and its actions as ledger lines you can read at a glance. file names are real paths — click one and the finder opens on it. the box at the bottom speaks to the real session, not a copy, and it never refuses you: a session mid-thought holds your note and sends it when it settles.
Refactor the parser — keep the public API.
Starting with the hot loop; the tokenizer allocation is the real cost.
›Edit src/parser/core.ts
›Bash pnpm test — 41 passing
Ship it.
three ways to work
choose a mode whenever a conversation is waiting for you. most work stays fast and direct; the difficult work can bring claude and codex together without giving two processes permission to edit the same tree.
your existing conversation handles the task exactly as it does today.
your agent writes. the other reads the real diff, reports actionable issues, and your original agent resolves the valid ones.
both plan and improve both views, then both vote. disagreement creates a hybrid; without mutual approval, nothing starts.
every drop carries its uncommitted weight — green and red, embedded in the field. open the working tree to see each file with its proportional bar, then commit on one click: boum runs git add and git commit in that repository. your hooks run. nothing is ever pushed.
sync/replay.ts+214−38
sync/journal.ts+96−12
sync/replay.test.ts+142
›commit 3 files — “rewrite the sync engine”
the calm view
the same sessions, as a room instead of a wall: each project a drop of glass, luminous while its agent works, resting when it lands, amber when it needs you — and the light streaming toward it is the tokens being spent, live. it settles into a low-frame screensaver cadence when left alone. tab again and the wall comes back exactly as you left it; the field releases its renderer completely.
trust
boum reads the session files claude code and codex already write on your machine. there is no boum backend, and boum never edits your code directly. when two engines work together, every consultation is fresh and read-only; only the original conversation can implement the task you sent.
resumes through your own CLI — same session, auth, machine, and working tree.
gets no write tools and no persistent session; its plan or review is validated.
starts from your message. stale trees and failed agreement stop before edits.
how it works
no setup, no import. it finds every claude code and codex session on your machine and gives each one a pane.
six conversations at once, arriving as they are written. amber is a question. the strip above says what needs you.
cmd-2 to move, then type — no click, no hunting for a window. commit from the foot when the dust settles.
“i don’t watch my devs write every line. why would i watch claude?”— the whole idea, in one line
questions
a macOS app that gives every claude code and codex session on your machine its own live pane, side by side — the conversation as it is written, what each one is doing, and what it needs from you. you answer any of them from the keyboard, commit from the same surface, and press tab for the calm view when you would rather just watch.
your existing claude code and codex sessions remain the source of truth. boum reads the files they write and, when you send an instruction, resumes that exact session with your own CLI and auth. in pair or dual mode it also starts fresh, read-only consultant runs; only the original conversation can write. a session you started in a terminal keeps working there.
boum does not edit source files directly. your message can resume the original agent session, which may edit just as it would from the terminal; team-mode consultants receive read-only tools. the separate commit control runs git add -A and git commit in that repository — your hooks run, and nothing is ever pushed.
there is no boum backend. the app reads local files and invokes the CLIs you already own; model traffic goes from those CLIs to their providers under your existing auth. boum itself checks only for app updates.
yes, when the extra work is worth it. solo is the fast default. pair review lets one implement and the other inspect the real diff read-only. dual plan has both independently plan, improve both proposals, and vote; disagreement triggers a hybrid round, and without mutual approval nothing is implemented. you can switch modes whenever the conversation is waiting for a new message.
codex is supported the same way claude code is — its sessions get panes beside the rest, and you can raise new work on either backend. other agents will follow when they can be observed just as faithfully.
free during the open alpha — and early users keep it free when boum becomes paid.
boum is an early alpha, built for hobby and side projects. work starts only from your explicit message, consultants are read-only, and the original session is the sole writer, but you should still review agent output and commits as you would in a terminal.
a mac on apple silicon (macOS 14+) and claude code, codex, or both. that’s it — open boum and your sessions are already there.
free during alpha · v0.0.21 · apple silicon & windows
early alpha — for hobby & side projects, not production work