PlanQueue

Running more than one coding-agent session at a time means remembering what each terminal is trying to do. The plan lives in your head, or in a file you keep beside the terminal, and every next prompt means opening the right file, finding the step, selecting the line with the mouse, copying it, switching windows, and pasting it into the agent. Each action is small. Repeated on every step, in every session, it breaks your flow.

I got to the point of running 10 to 20 sessions this way, with a Markdown file beside each terminal, and tried several variations of the same idea before this one. The root cause was always the same: the plan and the session were two separate artifacts. A little of the plan got lost on every trip between them, and the rest stayed in my head instead of in text.

PlanQueue removes that transcription step. It is an MIT plugin for Oh My Pi (OMP), a terminal harness for coding agents. It renders a session note below the status line and runs that same note as a prompt queue. The note you read is the note you run.

Each top-level line is a markdown checkbox task: pending, in flight, done. Ctrl+Down dispatches the next line to the agent; indented lines below it ship together as a multi-line prompt. Ctrl+Shift+Down toggles auto-run, which drains one task at a time while you do something else.

A lone line of three dashes (---) is a human checkpoint: auto-run stops there and waits for your review. Put one before anything irreversible and the rest runs on its own. You write the whole path while the idea is clear and decide exactly where the agent has to stop and wait for you.

The part I did not plan and now use the most: the agent writes its own queue. Say "add to the list" mid-conversation and it appends a task. /make-note decomposes a goal into a ready-to-run queue, checkpoints included. /rebuild-note re-plans from the whole session, keeping only what is still left to do.

Everything is plain Markdown, per repo, branch, and session, under ~/.planqueue, with an append-only history file beside it. No database, no separate app. /planqueue browses the notes of parallel sessions on the same repo and branch. The pure logic (paths, queue, editor, config) was extracted into @aryrabelo/planqueue-core, testable with bun test and usable outside OMP.

The honest limit: OMP caps continuation chains at 8, so an auto-run without a checkpoint pauses after roughly 8 tasks, and it also pauses on errors. The fleet view across workspaces comes from pairing it with Herdr. The goal was never to remove you from the work. It is to keep the path out of your head and put your attention where a decision is needed.

Install with omp plugin install github:aryrabelo/planqueue.