Let the agent use the studio, then take the timeline back
The agent is useful when it can touch the project you already have open: read the footage, write the edit, and leave a timeline you can still change.
The agent sits in the client
StarCut’s agent can call tools where the project is open. Chat and resume travel over SSE or WebSocket. When the agent needs the studio itself — to read the timeline or write an edit — that tool call comes back to the client over HTTP or WebSocket. The work lands in the project, not in a separate inbox.
That is why you can scrub the result. Captions, generated audio, and timeline edits are part of the same studio you were already using. Taking the timeline back means changing those edits yourself after the run, or instead of asking for another one.
One session, one run
Several clients may watch one agent session. Only one run holds the lease, so a second tab does not start a competing edit. If the connection drops, resume the same session rather than opening a new one and hoping the two histories match.
Watch the timeline while the run is in progress if you want, but wait for the lease to free before you ask for a different pass. The project keeps what the run already wrote.
Walkthrough: ask for the cut, then change it
Start from footage you can name. A short promo is enough to see whether the agent edited the project or only described an edit.
- 01Open the project in the browser. Confirm the footage is in the project, not only attached to a chat somewhere else.
- 02Tell the agent the cut: length, which shot stays as the master, where captions should sit, and the kind of score you want.
- 03Let the run call tools in that client. You should see the timeline change, not only a paragraph describing what it would do.
- 04When the run finishes, change one thing by hand. Move a caption, trim a shot, or mute a beat. If you can, the agent used the studio.
- 05Close the page and resume the same session later if the run was interrupted. Do not start a second run against the same project while the first lease is still active.
Drive the same studio from another agent
The agent inside StarCut is not the only way in. Supported hosts can connect through the StarCut plugin and MCP, then work against the same kind of project. The install path depends on the host — ChatGPT, Claude, Cursor, and the others listed on the plugin page — so follow that guide instead of guessing the prompt.
External or not, the check is the same. After the agent stops, the project should still be editable in the studio. A plugin that only returns a video file has not used StarCut.
A client-side agent does not hand you a file from somewhere else. It works in the studio that is already open.
Questions
Does the agent edit the project, or only reply in chat?
It can call tools in the client that has the project open, including reads and edits that show up on the timeline. The chat is how you ask. The project is where the work goes.
What happens if the connection drops mid-run?
Resume that session. Chat and resume use SSE or WebSocket, and a second overlapping run does not take the lease while the first one still holds it.
Can I use StarCut from ChatGPT, Claude, or Cursor?
Yes, through the StarCut plugin and MCP on supported hosts. Use the plugin page for the install prompt and the host-specific guide.
Open the studio
Cut in the browser, keep the timeline editable, and install the plugin when another agent host should drive the same project.