one window conducts

A conductor for the whole epic

/k0-ultracode turns one Claude Code session into a conductor: a window per story, driven from plan to merged work in order, tested and counter-checked.

Since k0 0.13.0

An epic is several sessions, and somebody has to keep the thread

An epic of eight stories is eight Claude Code sessions, each asking you things at its own moment. Knowing which one is waiting, which is ready to merge and which can start now is work in itself — the kind that gets lost between windows.

/k0-ultracode on an epic makes one session the conductor. It does not plan and it does not write code. It opens an ordinary session for every story — a real window, its note going live and moving through the columns on its own — and drives each one through its plan and its work, in the order the arrows between the stories allow.

You see it, and you can step in anywhere

The conductor puts a note of its own on the board, marked Conductor, with an arrow to every story it drives. Every window stays yours: type into any of them whenever you like. While one session asks you about its plan you can be answering another. Ask the conductor where are we? and it answers with a line per story; when a window needs you — a question, a plan to approve — it tells you which one by name, and notifies you if you have stepped away.

It merges the stories one at a time, so two windows never land on your branch together. Each session finishes in its own worktree and says it is ready; the conductor merges it, runs the tests on your branch, has the change read by an agent that wrote none of it, sends repairs back to the session that knows the code, and checks the story against every decision. The story goes to Review, and whatever was waiting on it starts.

How to use it

  1. Open the epic's panel and press Ultracode, or type /k0-ultracode K7 in a new terminal.
  2. Answer once: how much rope (interactive, checkpoint or autonomous), how hard (two, three or five sessions at once) and when the plans are made (as they come, or all first so every question is asked in one sitting).
  3. Answer the windows it sends you to. Ask it where are we? whenever you like.
  4. Press Done on the stories in Review when you are happy with them.

Small print

It never pushes and never presses Done, and it stops when its repair attempts are spent, saying what is still broken. Everything it does is written in its note's Log, so a conductor whose terminal you closed is started again on the same epic and carries on where it was. In autonomous the sessions start with every permission skipped.

Keep reading

← Work next door, merge back All features Your board, on every machine →

k0 is in early access. Leave your address and you will hear when your account is ready.

Get early access