Scene Flow Shop

Workflow automation for video

Video editing automation, from batch edits to auto-build

Repetitive editing is where time disappears. Scene Flow Shop automates it with batch operations, bulk transitions, an auto mode that builds a rough cut unattended, and a render queue that works in the background.

Automation you can use today

  • Auto mode

    The assistant applies its own proposed edits without waiting for approval, carrying out a multi-step build such as scenario → timeline → prompts → transitions in a single request.

  • Batch edits

    Trims, moves, speed and volume changes, transitions and gap closing combine into one call: one approval, one undo step.

  • Bulk operations

    Add crossfades between every pair of adjacent clips, remove all transitions, or close every gap on a track in one command.

  • Scenario to timeline

    One step turns an approved scenario into scenes, tracks and placeholders.

  • Projects as templates

    Export a project as a file and import it as a starting point for the next one.

  • Background rendering

    Preview and final renders run on a worker queue while you keep editing; failed renders are refunded.

Automation with guardrails

Approval is the default. The assistant proposes exact tool calls and you decide, so automation is something you turn on rather than something that happens to you.

Even in auto mode every edit is version-checked, recorded with who made it, and undoable. If your credit balance runs out mid-build, the assistant stops cleanly instead of failing halfway.

Example: idea to rough cut

  1. Describe the film

    One message with the idea, the tone and the target length.

  2. Turn on auto mode

    The assistant creates the scenario and applies it to the timeline.

  3. Bulk-polish

    Ask for crossfades across the video track and gaps closed, each in one batch.

  4. Review and export

    Undo anything you don't like, then render a preview.

Where MCP fits in

Because every operation is one of 53 MCP tools, the same building blocks that power auto mode are the foundation for wider automation. Read more on the MCP tools page.

Frequently asked questions

Does auto mode ask permission for each edit?

No, that's the point of auto mode. You give one instruction and the assistant carries it out. Everything remains versioned and undoable, and approval-first mode is the default.

Can I trigger automations from my own scripts?

There's no public API or scheduler today. Automation currently happens through the assistant, batch and bulk operations, and auto mode. The MCP tool surface is the foundation for external automation.

What happens if I run out of credits during auto mode?

The assistant stops and tells you. Edits already made stay in place and can be undone; buy credits or use your own Anthropic key to continue.

Can I reuse a project's structure?

Yes. Export a project to a file and import it to start a new one from the same tracks, scenes and timeline.

Explore more