Four modes
How awake the machine stays while sessions run — including working with the lid closed, which caffeinate cannot actually do.
Project
k0
Early accessk0 is the kanban board I built for my Claude Code mess: one card per session, one column per project. Cards take the colour of their status, the ones that need me rise, and double-clicking brings back the real terminal.
atlas-api 3 ↑ 4
atlas-api 210 MB
Fix-Webhook-Retries
Retries were firing twice on a 429. Backing off properly and adding the test that catches it.
4 min
atlas-api 180 MB
Rotate-Signing-Keys
Second key accepted for verification before it becomes the one we sign with.
22 min
atlas-api
Drop-Legacy-V1-Routes
2 h
pier-web 3 • 6
pier-web
Dark-Mode-Tokens
Every color through a token, so the two themes stop drifting apart.
session closed 1 h
pier-web 260 MB
Checkout-Empty-Cart
Reproduced the blank step when the cart expires mid-payment. It is a race, not a render bug.
11 min
pier-web 95 MB
Trim-Bundle-Size
Date library was pulling every locale. Down 190 KB.
3 days
northwind-etl 2 ↑ 11
northwind-etl 150 MB
Dedupe-On-Two-Keys
Two identical rows survived the merge. Found out why, and it was not the key.
38 min
northwind-etl 340 MB
Rewrite-Import-Parser
Streaming the file instead of loading it whole. Nine thousand rows no longer eat the machine.
6 min
kite-mobile 2 ✓
kite-mobile
Push-Token-Refresh
Tokens were going stale after a reinstall and nobody noticed for a month.
session closed 5 days
kite-mobile 190 MB
Offline-Queue
Actions taken with no signal land when it comes back, in the order they were made.
19 min
sandbox 2 ✓
sandbox 120 MB
Try-Local-Embeddings
Whether the small model is good enough to keep the whole thing on the laptop.
31 min
sandbox
Read-The-Sqlite-Docs
1 day
Why it exists
You open a Claude Code session in one repository, then another in a different one, then a third because the first is still thinking. Running five, ten, twenty sessions at once is not hard. Claude Code does not mind.
What is hard is knowing which one is done. Which one asked you a question three minutes ago. Which one is just sitting there, idle, waiting on a yes you have not given it yet.
So you click through terminal windows, one by one, checking. That is the actual bottleneck. Not the AI. You.
Seven colours, one board
A card is the colour of its status, and you never pick one yourself.
- Needs answer It is asking you something.
- Needs approval It finished a plan and wants your yes.
- Your turn The terminal has gone idle.
- Working Leave it alone.
- Planning Working, inside a plan.
- Backlog An idea. No session yet.
- Done You closed it. Off the board by default.
That list is also the sort order of the board, so the cards that need you rise straight to the top. Answer the red one and it goes back to work — it turns blue and sinks down its column on its own. You never drag anything.
A menu-bar icon takes on the colour of your most urgent card, and sits as a plain outline the moment nothing is waiting on you.
Your real terminal
Double-click a card and that session's terminal window comes to the front — even if it was minimised behind six others. That is the whole interaction, and it is how you drive twenty sessions from one screen.
k0 does not embed a terminal. No PTY, no hooks, no second copy of the thing you already have open and already know how to use. It drives the terminal you already have: Terminal.app on macOS, tmux on Linux, Windows Terminal on Windows. It works out what each session is doing by reading Claude Code's own files, not by watching over its shoulder.
- Shift+Enter gives you a new line instead of sending the message.
- Cmd+V pastes a screenshot — it lands in the session as an image, in a plain terminal.
- Each card shows how much memory that session is using.
- Sessions are born in plan mode, so nothing runs before you have seen the plan.
And a few other things
A git mark on everything
Uncommitted files, unpushed commits, or a quiet tick when everything is safe. It never runs fetch.
A document viewer
Only documents — md, txt, PDF, Word — instead of every source file in the repository.
Import
Fills the board with the sessions you already had, including the ones you opened by hand.
Where it is now — October 2026
Up to 0.5.0, k0 was the local tool I built in August: free, MIT, no account, on npm. It read Claude Code’s own files and brought the real terminal forward. No terminal inside the app.
Since 0.6.0, October 2026, it is a product. Accounts open on approval. The board still runs on your computer and works offline, but keeps a copy in k0 Cloud, on Supabase in the EU. That means a lost laptop hurts less, a second computer catches up, and the browser can read it, read-only. K numbers now live per account. The code is source-available under the Sustainable Use License, not open source; 0.5.0 and older stay MIT.
Free plan, privacy, terms, all the boring bits: k0-board.com.
Try it
Early access is on k0-board.com. Nothing is charged during early access. The code is on GitHub. Questions go to hello@k0-board.com.