Handover between repositories
A session that finds work belonging to another repository hands it over, and the session there picks it up.
One short page for each thing k0 does, and why it does it.
Every session is a sticky note, and its colour says whose move it is — yours or Claude's.
The same stories two ways: a board of notes for the day's work, and rows of epics, stories and tasks for planning it.
Sleep, Away, Nerd, Driving: one click says how awake the machine stays while Claude Code works, lid closed included.
Mark a note always active and k0 never closes its terminal for sitting idle — for a session left watching a deploy.
k0 shows what each session weighs, and after twelve idle hours closes the forgotten ones. Resume picks them up again.
Every note is a real Claude Code session in its own terminal window. Double-click the note and that window is in front.
Press ⌘K, type a number, a word of the title or of the notes, and go straight to that session's terminal.
What you did across every repository — what is online, and what only looks finished — written up like a release note.
After an update, a page says what changed since the version you had — in your language, as plain or as technical as you like.
Hold Control, speak, let go — the text lands where the cursor is. Offline, in place of Wispr Flow.
What every session consumed, by model, effort, repository and account — and how full your limits were, from your statusline.
Open a repository's documents in a tab — what the session changed, a search that finds them, and one click from Claude's reply.
Epics, stories and tasks, discussed in rounds, every decision written down — and the finished work checked against each one.
Drag an arrow from one note to another, across repositories, to say this one waits on that one.
/k0-work builds a planned story in its own git worktree, keeps a log as it goes, and merges back into the branch it came from.
/k0-ultracode opens a Claude Code window for every story of an epic, drives each from plan to merge, and tells you which one needs you.
Sign in with GitHub or Google and the board keeps a copy in k0 Cloud — your code never goes with it.
/k0-import puts the Claude Code sessions you already had on the board, each with a title and a line saying what it was about.
A mark on every note and column says what is not committed or not pushed; a globe says whether the dev site is running.
A session that finds work belonging to another repository hands it over, and the session there picks it up.