The co-writer
Ask the co-writer for beats, a branch, a tighten, a continuity check, or a bible rewrite, then accept or revert what it drafts.
The co-writer lives in the bar at the bottom of the editor: a prompt field, a row of action pills, a status line, and a budget meter. It is available to editors. If you have viewer access the bar says so and does nothing else.
The five actions
Each pill is a different kind of ask. The prompt field steers whichever one you press.
| Action | What it drafts | Needs a scene open |
|---|---|---|
| Continue scene | More beats for the open scene | Yes |
| Generate branch | New scenes plus the edges that wire them into the flow | No |
| Tighten dialogue | Replacement beats for what is there now | Yes |
| Check continuity | Findings only, nothing to write | No |
| Update bible | A rewritten story bible | No |
Press Enter in the prompt field to re-run the last action you used, which is Continue scene until you pick another. Below roughly 1100px wide the pills fold into a single Actions menu with the same five entries.
The chip inside the prompt field names the scene the co-writer is reading. If a pill is disabled, the hint tells you why, usually "Open a scene first."
Draft, accept, revert
Ask
Type an instruction, then press an action pill. The status line reads "Thinking…" while the request is out and "Writing…" once output starts arriving. Continue scene, Tighten dialogue, Check continuity, and Update bible stream, so cards appear one at a time. Generate branch does not stream: a half-arrived graph is scenes with edges pointing nowhere, so it arrives whole.
Read the draft column
The column opens beside the script, not over it, so you can judge the draft against what is already there. Beats and generated scenes come with checkboxes. Findings and a bible rewrite have nothing to tick.
While a run is still streaming the only button is Cancel. Accept is deliberately absent mid-stream: accepting half a stream would write half a thought.
Accept the part you want
Untick anything you do not want, then press Accept. The button counts what is ticked, so it reads "Accept 3 selected". Regenerate runs the same instruction again from scratch. Discard throws the draft away (on a continuity report the button says Dismiss instead).
A restore point is taken before anything is written. If that fails, nothing reaches your documents.
Revert if you change your mind
After an accept the column stays open holding a Revert button. Revert asks for confirmation, then rolls every document back to just before that accept, server-side. It survives a reload and it works for everyone in the project, which is why it beats Ctrl+Z here.
If a run comes back with nothing to draft, the column shows an error rather than a zero-item draft to "accept". The usual cause is a conversational prompt sent to a drafting action, for example asking Continue scene to suggest a title. That attempt still spent a little AI budget.
Aiming a tighten at specific beats
Tighten dialogue rewrites beats. To say which ones:
- Select the beats in the script.
- Press Mod+Shift+K (Ctrl+Shift+K on Windows and Linux).
- Type your instruction in the prompt field, which now has focus, and run Tighten dialogue.
The draft column names the beats an accept will replace. Without a selection the shortcut does nothing but say "Select the beats you want rewritten first." Firefox on Windows keeps Ctrl+Shift+K for its own console, so the Tighten dialogue pill remains the way in.
Refining a draft
Ask again while a draft is on screen and the second ask refines the first: "shorter", "colder", "keep line two". Up to three earlier exchanges travel with each request. Regenerate is different: it is a second attempt at the same instruction, so the rejected output is not sent as history.
Accepting or discarding ends the conversation. The next ask starts fresh, which is what you want, because accepted beats are now in the scene and the co-writer reads them from there.
Past conversations
The spark button at the left of the bar drops down your recent conversations, newest first, titled by their first prompt. They are stored on the server, so you can close the tab and come back.
Reopening a conversation replays it into the draft column. If its draft was already accepted, the column opens holding the Revert instead of a second copy to accept. A conversation that is no longer available says so rather than opening empty.
What the co-writer is told
Every request carries the story bible, the cast, the variable declarations with their types and choices, the asset list (ids only, plus the animation clip and expression names it may use), the summaries of scenes on the path into the open scene, the scenes around it, the compiler's current errors and its unreachable and dead-end scenes, and the open scene's script.
That is why it can only reference ids that exist. It is also why continuity findings agree with the problems panel: the compiler's verdict is sent as fact rather than left to the model.
The bible is the part you control. See the story bible.