Runs and review

A run is one piece of agent work: your prompt, a plan, the commands it executed, and the review branch they landed on. This page walks one from start to merge. You need editor access.

Start a run

Watch it work

The chip at the top of the thread reads writing · batch N/M: how many batches have opened, out of the phases the plan promised. Under it the feed fills in as the run goes:

• Batch groups, headed by the phase goal, with one row per command. A plus for things created, a pencil for edits, a minus for deletions, and a ◫ badged AT MERGE for held chapter commands.
• Deleted text, shown struck through on the row that removed it. The ledger keeps what was removed, because after the command runs the document no longer has it.
• Checkpoint dividers at each phase boundary, labeled with the phase's goal.
• The credits meter in the footer, spent against the pool of whoever started the run.

The feed comes from the run's ledger on the review branch, not from your browser's memory. Close the tab, reopen the project, and everything is still there. Other editors see the same feed and a chip in the header that says the agent is writing.

Stop raises a stop flag. The run finishes the phase it is in, takes its checkpoint, and goes to awaiting review. The chip reads "stopping after this phase…" while that happens. There is no mid-phase abort: a half-executed phase would make the ledger lie about what it did.

A run also stops at a phase boundary when credits run out. What it wrote up to that point is still on the branch, still reviewable, still mergeable.

Review the draft

When the run finishes, the chip reads "awaiting review" and the Review changes button lights up. Press it. The editor navigates to the run's review branch and changes shape:

• An AGENT DRAFT banner across the top with the prompt, the counts ("12 changes · 2 deletions · 1 held at merge"), and the branch name.
• The ledger in the side column, read-only, grouped by phase.
• Marks in context: chapters and scenes the run touched are flagged where you normally work, including "agent deletes this at merge" on a chapter it wants gone.

Click any ledger row that points somewhere and the editor jumps to it: a scene row opens the scene, a chapter row selects the chapter, an edge row opens the flow view.

Read the draft the way you would read a collaborator's work. Play it. Edit it by hand if a line is nearly right, since the branch is not locked. Your manual edits are not in the ledger, but they merge along with everything else.

Rewind a phase you did not want

Each batch group except the last has a Rewind to here button. It rewinds the draft to the checkpoint at the end of that phase: the later batches leave the draft, and any held chapter commands in them are voided and shown as VOIDED.

The confirm dialog lists the batches that will be dropped by name. Nothing has touched main at this point, so a rewind costs you only the agent's work, not your story. You can rewind, then keep going in the same session with a new prompt if you want the later phases done differently.

Rewinding is tail-only. You cannot remove a phase from the middle and keep what came after it.

Merge

Merge into main asks first, and the dialog itemizes every held chapter command by name, so "Delete chapter Act Two" is said out loud before it runs.

Confirm and the merge runs in stages. The button reports progress: "Merging… 3/7 docs" while documents are combined, then "Applying chapter changes…" while the held chapter commands execute in ledger order. When it finishes you get a toast, a post-merge checkpoint exists in the project's history, the session closes, and you land back on main.

If some documents fail, the banner says which ones and offers Retry. Retrying is safe: documents that already merged are unaffected.

Discard

Discard sets the whole draft aside. The dialog spells out what that means: every change on the branch is set aside, nothing has touched main, held chapter commands are voided, and the run's checkpoints are kept. The session closes.

Discarding is the cheap option and it is meant to be used. A run that went sideways costs you the credits it spent, nothing else.

After merge or discard

The session is closed. A follow-up prompt in that thread is refused with "This session is closed, its draft was merged or discarded. Start a new one." The studio starts a new conversation for you with the same prompt, forked from your now-current main.

Before merging, follow-ups are different: a new prompt on an open session runs on the same review branch and appends to the same ledger. That is how you say "good, now do the endings too" without opening a second draft to review.

One run at a time per project. A second task prompt while a run is writing is refused with "A run is already in progress on this project." Talking to the agent, though, is always allowed: see steering.