The agent
The chat
On this page
The chat is where you talk to your agent. It’s a panel on every page in Pro, on the far right unless you move it, and on the right in Lite. Ctrl+K puts the cursor in its box, and Ctrl+Shift+K shows or hides it.
Ask for something
Use plain words, such as “tighten the second half by a few seconds”. What the agent changes shows as a proposal.
- Add pictures. Paste them into the box, or grab a frame from either viewer with +.
- Name a source. Type
@. - Say what goes along. A chip shows what goes with the message: the timeline, the playhead, the selection and the marks. Click the chip to leave them out.
Pick the agent and how it works
| Control | What it does |
|---|---|
| The top | Picks the agent and its model. It also shows how full the conversation is, the past conversations, and a button for a new one |
| Act | The agent works on it straight away, on its own |
| Plan first | The agent reads and looks, then shows a plan card before it edits. It works on its own once you approve |
| Effort | How hard the agent thinks: Low, Medium, High, Extra high or Max, as the model offers them |
Read the answer
The answer folds the agent’s steps into groups, with the frames it looked at, and shows the proposal while the agent works. It ends with how long it worked and Go back to before this, which undoes what it put on the timeline.
Just over its last words, what the engine found: the brief, item by item, with what was missed first (“Brief · 4 of 5 met”), then any problem the checks found that the cut didn’t have before, or “Checked: no new problems”. The brief is what your ask set that can be checked, such as a length or words that must be heard. This comes from the engine, not from the agent’s words, so you can read a claim in the answer against it. Before it keeps a cut, Nolan Edit and Claude Code also ask a reviewer that sees only the cut to judge it, and fix what it finds.
The Claude Code agent writes its answers for an editor: timecodes and source names. To stop a run, press the square button. Any batches it already sent stay in its proposal, which waits for Keep or Discard (see Proposals).
What’s still running
A script or a render the agent leaves running in the background shows over the chat box, with its mark and how long or how far it has gone, so a turn that ended with a render going on doesn’t read as finished. Each one ends as done or failed.
Agents it sends out
Claude Code can send out agents of its own for a piece of the job, such as reading the music while another checks the cuts. Ask for it in plain words, or let it decide. Each one keeps a short line in the chat, with a mark while it works and a check when it’s back. Their edits come back in the same proposal, and the frames they look at go to the same place as any others: the agent you chose.
Answer its cards
Three kinds of card show in the answer and wait for you. Question and plan cards come with Nolan Edit and Claude Code.
| Card | When | Your answers |
|---|---|---|
| Question | The agent is unsure and a wrong guess would waste work | One of 2 to 4 options, the recommended one first, or your own words. An option may show a small preview. Unanswered, it goes with the recommended option after 10 minutes |
| Plan | Plan first is on | Approve, Edit (say what to change, and it plans again) or Reject |
| Ask | With Nolan Edit, before a shell command, a file it writes, the web, bringing media in, rendering or a setting. Rarely with Claude Code, whose auto mode lets safe steps through and asks only about a step it can’t judge safe | Allow once, Always allow (that tool, for the rest of the conversation) or Deny |
Stopping the conversation withdraws any card still waiting. Notes and style says how to set when it may ask.
Past conversations
The clock icon at the top of the chat lists past conversations, and the pencil starts a new one. They’re kept in the project’s folder, with their steps, the frames the agent looked at, the cards and your answers, and the proposals they made.
While it works
You don’t have to watch.
- Switching to another project, going Home, closing a window or switching between Lite and Pro never stops a run. Closing the project does, and it asks first.
- Several projects can each have an agent at work. When one in another project finishes, fails or asks you something, a toast says so.
- An update, a restart or a crash only pauses a run. The next start opens the project again and the run carries on in the same conversation. The chat marks the place: “Paused for the update · carried on 14:02”. A card that was waiting waits again, with its time restarted.
Next
Proposals covers what happens to the agent’s edits. Keys has the chat’s keys.