Using the pane

Two places to watch a job: the pane beside the chat in Claude Code, and the daemon's screening page in a browser.

#The /rapid command

With the plugin installed:

Node ids are the n_… ids rapid job <id> and the pane show. status, approve, and redo need the daemon; when it is down they answer daemon not running: run `rapid serve` . new starts one itself (through rapid video), and the pane's Start daemon button runs rapid daemon ensure. Asking Claude in plain words goes through the MCP tools.

#The pane

The pane follows the newest job, or the one you pick when there are several. It shows:

• The job: its title and progress.
• The graph: every node by state, grouped by scene, growing as the planner adds nodes. Stale branches show as they run again. In the terminal, where there's no SVG, it's drawn as rows of glyphs with a legend.
• Needs you: every approval waiting and every failed node, with why, and buttons: Approve (approvals only), Redo, and Open.
• Lanes: a row per lane with its running and queued nodes and how long each has waited or run.

The status line says the job's progress, and a notification arrives when something needs you or a job finishes or fails.

The pane reaches the daemon by running the rapid CLI every two seconds. When the daemon is down, it says so, shows a Start daemon button (which runs rapid daemon ensure), and checks less often until it's back. If rapid isn't on Claude Code's PATH, set the plugin's cli option; see install.

#The screening page

In Claude Code, /rapid:open opens it at the newest job: beside the chat when the app has a browser pane, in your browser otherwise. In a terminal, rapid open [job] does the same. Or open http://127.0.0.1:4317 while the daemon runs. It's the same daemon, so it updates live from the event stream.

The header holds the wordmark (back to every job), where you are (the job, then a node, a scene, or the brief), and whether the page is live: a dot and "live" while the event stream is connected, "reconnecting…" or "offline" when it drops, with the daemon's address and the last event's time on hover. Hover or focus anything with more to say (a state, a lane, a card, a format, a cut-short name) for a short explanation. A node that needs you is called waiting everywhere on the page.

• Every job (#/): one table of jobs, grouped under each folder rapid projects finds projects in (~/rapid unless you add others), then the jobs in folders under none of them. Each row is a job's state, its title, its project folder, its format (a small box in the frame's shape), and when it ran; click it to open the job. Add folder at the top finds projects in another folder, and New video beside a folder takes a line or two of brief and starts a video in a new project folder there, in its default style with no stops. A job whose project folder was moved or deleted says "folder gone", and its pages say the folder is gone instead of showing files that no longer load.

Every other page is a sidebar on the left and the page itself on the right. On a phone the sidebar sits above the page, its head shown and the rest behind details.

• A job: in the sidebar, its title, state, format, and folder; its scenes (click one to glide the canvas to its row, or open to open the scene); its brief, folded to a few lines (more… opens it whole); what is waiting on you, each with Approve (approvals), Redo (with a note), and Open; what the video chose without you; and the lanes' running and queued nodes ("all idle" when there are none). Beside it, the graph on a canvas: the stages as columns (look, storyboard, key frames, rounds, video), each scene a row, edges for what each node needs, each node a card with its poster, state, and lane. Drag or scroll to pan; pinch or ⌘-scroll to zoom; Fit shows it all. New nodes arriving never move what you are looking at.
• The brief (#/job/<id>/brief): the job's whole brief, to read, beside the job's sidebar.
• A node: in the sidebar, its facts (type, lane, group, attempt, how long it waited and ran, what it needs, its error) and, when it is waiting on you, its actions; beside it, its outputs, each with its path and size and a preview by its kind (a picture, a sheet, a player, the start of a scene's code, a review's verdict, marks, and answers, a storyboard's scenes), and its log, with JSON lines read as key: value and the project's paths relative to it.
• A scene: the player with a frame scrubber and the scene's marks along it, and its key frame and contact sheet; in the sidebar, the job's scenes, a new mark, and every mark on it.

#Marking a moment

On a scene's page:

1. Pause, and step frames with the arrow keys (Shift for ten) or the frame buttons. Space plays and pauses.
2. Click the picture to pin a moment, or drag to box a region.
3. To mark a span, move the playhead and press Extend to playhead.
4. Write what should change, pick a severity (blocker, major, minor, nit), and press Send.

A mark is stored against the scene's current version and shown to everyone watching. It has the same shape as a reviewer's mark, and it's written to renders/<scene>/marks.json in the project, which every build of the scene reads first. To have the builder act on your notes now, redo its build node with a note (/rapid redo <node> <note>, or Redo on the page): that starts the scene again, with your marks and the note.

Write notes the way a reviewer does: what to change and where, not just what's wrong.