An AI agent that feeds Final Cut Pro

What the agent does for Final Cut

EditAssist builds the cut and hands it to Final Cut in the format Final Cut speaks: FCPXML. The agent assembles rough cuts and selects timelines from intent, whether that's a transcript, a shot list, or director's notes. It auto-syncs external audio, builds multi-cam, conforms offline edits to camera originals, and reframes masters for social. Those results arrive in your library as timelines and events, ready to refine.

• SpliceKit bridge

  Connects the agent to Final Cut for cut handoff.

• Workflow Extension

  Reach the agent from inside Final Cut Pro.

• FCPXML drop-folder

  Drop generated FCPXML straight into your library.

• Rough-cut assembly

  Build cuts and selects from transcripts and notes.

• Conform

  Relink offline edits to camera originals; flag mismatches.

• Reframe & deliver

  Reframe masters and prep against 32 delivery specs.

How the bridge works

Final Cut Pro's magnetic, library-based model is different from a track-based NLE, so EditAssist meets it on its own terms. Three paths connect the agent to Final Cut: a SpliceKit bridge, a Workflow Extension you open from inside Final Cut Pro, and an FCPXML drop-folder that ingests the agent's output into your library. You ask for a cut; the agent assembles it from your indexed footage and delivers it as FCPXML that Final Cut imports as a timeline.

The same agent is reachable from the EditAssist desktop app, the terminal, or a Telegram message, sharing the same project context and memory. Final Cut Pro support is macOS-only, in step with the application itself.

Commands you can give it

You work by describing the outcome. A few Final Cut-specific examples:

• “Build a rough cut from today's interview footage and drop it into my Final Cut library.”

• “Assemble a selects timeline of every close-up of the lead and hand it back as FCPXML.”

• “Find the three best takes of the monologue and lay them out side by side.”

• “Conform the offline edit to the 6K camera originals and flag any relink mismatches.”

• “Generate a paper edit from the transcript, keeping only the answers about funding.”

• “Auto-sync all four camera angles and build a multicam from the shoot.”

• “Cut a 90-second highlight reel from yesterday's footage set to the temp score.”

• “Reframe the 16:9 master into 9:16 and 1:1 versions for social.”

Hundreds more across every workflow live in the prompt library.

Assembly, conform and interchange

Final Cut editors get the full weight of EditAssist's assembly engine without leaving their library. With every frame indexed and every word transcribed, the agent can build a paper edit from a transcript, assemble selects from director's notes, auto-sync multi-cam, and check loudness, then hand the result back as FCPXML.

Because FCPXML is also an interchange format, the Final Cut path doubles as a bridge between suites: the agent can conform an FCPXML from Final Cut into DaVinci Resolve for grading, or move a cut toward Premiere Pro. It conforms across FCPXML, FCP7 XML, and CMX3600 EDL, and preps deliverables against 32 delivery specs.

Local-first by design

Transcription, vision analysis, embeddings, and search indexing all run on your own GPU. No frames are uploaded and no media is sent to a server. The only thing that leaves your machine is the text of your conversation with the agent. Your client's footage and your project files stay on your hardware. EditAssist runs on macOS (Apple Silicon, Metal), with Final Cut Pro support matching the application's own platform.