The assistant panel

Ask for a change in words and it happens on the timeline, as one undo step. It needs a project, because it works from your production rather than from a folder of files.

It issues commands, not edits

The assistant does not reach into the document. It calls the same timeline:* commands the keyboard and the toolbar call, which has two consequences worth knowing.

Undo behaves. A request that moves three clips is one step, because it was one intent, and pressing undo once puts you back where you were rather than a third of the way.

And whatever your editor personality is, the assistant is unaffected by it. Personalities remap keys onto commands; the assistant was already speaking commands.

The editor with the assistant panel docked

What it can see

Opened inside a project, it reads the production: the scene list, the shot list, and the takes uploaded against each shot. So “put the circled takes for scene 14 in order” is a request it can act on, where a folder of filenames would leave it guessing.

It can also change your selection, which is how “show me the insert” moves the playhead and highlights the clip rather than describing where to look.

Where it will not work

The assistant needs a signed-in project. The standalone editor at /cut and the desktop app in local mode both show a notice instead, because there is no production for it to read and no account to bill the model against.

It docks and floats like any other panel, and the conversation survives being moved between the two.