Every edit is a tool call

Make a cut in SmashCut's timeline. Now ask your agent to make the same cut. Under the hood, the identical thing happens: one tool call, same name, same arguments. The UI and the agent drive the same 53 tools. There is no second path.

Most software bolts automation on afterward — a macro layer, a scripting corner, an API that covers half the product. We built SmashCut the other way around. The editor is a set of tools; the interface is one operator of those tools; an agent over MCP is another. If a button can do it, an agent can do it.

One surface, two operators

That single decision pays for everything else. Agents get the full editor, not a subset: keyframes, color, captions, multi-track arrangement, batch export. Our bundled playbooks are just sequences of the same calls, so you can read them, edit them, or write your own. And when an agent works, you watch real edits land on a real timeline — not a black box rendering a result.

It also makes trust concrete. Because every change flows through a tool call, every change carries its author. Open the history and you see exactly which edits were yours and which were the agent's, call by call.

Undo respects the actor boundary

Attribution is what makes undo safe. An agent can undo its own work — and only its own work. Your edits are never on its stack. If a run goes sideways, the agent rolls itself back and your timeline is exactly as you left it.

That is the whole philosophy: one set of tools, two hands on the desk, and a hard line between them. It turns "let the agent try" from a leap into a habit.

Download SmashCut free for macOS and Windows and put an agent on your timeline.