Asking an AI to edit
Coeditor makes the first cut for you. It reads the transcript, plans every keep and cut with a reason, and builds the cut in Final Cut Pro, Premiere Pro or DaVinci Resolve, the editor you already use. It never overwrites your timeline. You then finish the edit there, the way you always have.
Full answer on its own page
More
How it goes with Coeditor:
- Make a project and add your footage (1 to 100 files). Coeditor stores file paths only, nothing is uploaded.
- Analyse. Coeditor transcribes, syncs any extra sources by sound and splits the footage into beats.
- Plan. Ask in plain words, for example "Cut this down to the good bits" or "Make it shorter".
- Review the story advice. Each item names its rule and only applies when you click Apply or say yes.
- Build. Coeditor builds the cut in your real project and never overwrites your timeline.
Coeditor can make a first cut for you to review. It reads your transcript, plans every keep and cut against 90 storytelling rules, shows the reason for each one and builds the cut in Final Cut Pro, Premiere Pro or DaVinci Resolve. You check it and finish the last stretch yourself.
Full answer on its own page
More
- What it does: footage becomes a transcript, the transcript becomes story nodes, and the nodes become a validated story plan. Then Coeditor builds it in your timeline.
- What it doesn't promise: a rule is advice, not a hard constraint, and a validated plan does not prove the story works for viewers.
- What stays with you: story advice applies only when you say yes, Coeditor never overwrites your timeline, and it keeps every earlier plan, so you can undo a plan and go back.
- Beta limits: private beta, macOS only, and for now installing needs a code checkout and Terminal.
Coeditor's ChatGPT route has not been checked in the beta. Agents can drive Coeditor over MCP, and Coeditor plans the cut with a reason for every keep and cut, then builds it in Final Cut Pro, Premiere Pro or DaVinci Resolve. That route needs a tunnel you run yourself.
Full answer on its own page
More
- How it connects: Coeditor runs on your Mac. ChatGPT would reach it over MCP through a tunnel you run yourself.
- Status: only the Claude Code route has been checked so far. ChatGPT is not yet checked in the beta.
- Where the edit lands: in your own editor. Coeditor never overwrites your timeline.
- Privacy: footage files are never uploaded. See "Does my footage leave my computer?" for what does leave.
Yes, through Coeditor. Claude drives Coeditor over MCP, Coeditor plans the cut against 90 storytelling rules with a reason for every keep and cut, then builds it in Final Cut Pro, Premiere Pro or DaVinci Resolve. Claude Code is the route that's been checked, and text chat runs on your own Claude subscription.
Full answer on its own page
More
- Claude Code: the checked route.
- claude.ai: needs a tunnel you run yourself and is not yet checked in the beta.
- Cost: text chat goes through your own Claude subscription (via Claude Code), so there's nothing extra to pay Coeditor for it.
- Privacy: footage files stay on your Mac. Transcript text goes to Anthropic through your Claude subscription, and still frames go to the model when it looks at them.
- Safety: Coeditor never overwrites your timeline.
The Grok route is unverified; Coeditor does the editing: it plans the cut with a reason for every keep and cut, then builds it in Final Cut Pro, Premiere Pro or DaVinci Resolve. That route needs a tunnel you set up yourself.
Full answer on its own page
More
- Intended role: Grok would steer Coeditor over MCP. The cut itself is built by Coeditor on your Mac.
- Status: only the Claude Code route has been checked so far.
- Your footage: the files are never uploaded.
- Your timeline: never overwritten. Earlier plans are kept.
An assistant such as Claude drives Coeditor over MCP, using the same tools as Coops, so it can analyse footage, plan the cut, give story advice and build in your editor. Deleting or replacing files it didn't make, touching another project and paid generation still need your approval in Coops on your Mac.
Full answer on its own page
More
- Tools: Through MCP, an assistant gets the same tools as Coops: analyse footage and read the transcript, save, read or undo a plan, get story advice, suggest, add or remove effects, build in your editor and make small edits, run long jobs in the background, search your footage, and check your plan usage.
- Approval: approve these actions in Coops on your Mac; approval in the AI app alone is insufficient.
- Status: only the Claude Code route has been checked. ChatGPT, Grok and claude.ai are not yet checked in the beta.
Coeditor never overwrites your timeline, and it keeps every earlier plan, so you can undo a plan and go back. It asks before deleting or replacing files it didn't make, or touching another project, and it treats text inside transcripts as data, not instructions.
Full answer on its own page
More
- Small edits after a build only change timelines Coeditor built.
- Paid generation asks first and shows the price first, with a per-story budget.
- Resolve imports your footage without moving the files.
- Undo: in Final Cut Pro, edits sit in the normal undo history. In Premiere Pro, use Edit > Undo. Resolve's scripting has no undo, so use Undo plan in Coeditor and build again.
- Story advice only applies when you click Apply or say yes.
- Footage files are never uploaded. See "Does my footage leave my computer?" for the full list of what leaves your Mac.
Inside your editor
Yes. With the Premiere MCP Bridge panel open, Coeditor builds its plan as a new sequence in your open Premiere Pro project, with the main footage on V1 and A1 and B-roll on V2. It never overwrites a sequence, and every keep and every cut comes with a reason.
Full answer on its own page
More
- You need: the Premiere MCP Bridge panel (Window > UXP Plugins), a Creative Cloud sign-in and an open project.
- What it writes: cuts, zooms as Motion > Scale keyframes (centred only) and cross dissolves.
- After the build: ask for small changes in plain words, for example "Remove the beat called Intro and close the gap".
- Limits: Coeditor can't undo inside Premiere (use Edit > Undo). Vertical builds have only been tested with test doubles so far.
Open your project in Premiere Pro and open the Premiere MCP Bridge panel (Window > UXP Plugins). In Coeditor, make a project with your footage, let it analyse, then ask Coops for the cut. Review the reasons and the story advice, then build. Coeditor makes a new sequence and leaves yours alone.
Full answer on its own page
More
Steps:
- Install Coeditor. In the beta this needs a code checkout and Terminal.
- In Premiere Pro, sign in to Creative Cloud, open your project and open the panel.
- In Coeditor, make a project and add your footage (1 to 100 files).
- Analyse: transcript, sync by sound, beats.
- Ask for the cut in plain words, for example "Cut this down to the good bits".
- Read the reason on each keep and cut. Story advice only applies when you say yes.
- Build. You get a new sequence with main footage on V1 and A1 and B-roll on V2.
- Polish by hand, or ask for small changes. To reverse a build step, use Premiere's Edit > Undo.
Yes, in DaVinci Resolve Studio with external scripting set to Local. Coeditor builds its plan as a new timeline, with main footage on V1 and A1 and B-roll on V2, and imports your footage without moving the files. Zooms are written inside a Fusion composition. Transitions have to be added by hand.
Full answer on its own page
More
- You need: Resolve Studio, with External scripting set to Local. No plugin.
- What you get: a new timeline. Your own timeline is left alone.
- Limits: Coeditor can't add transitions in Resolve, so add any dissolves yourself. Scripting has no undo, so use Undo plan in Coeditor and build again.
- Free Resolve: not yet checked. The live check used Resolve Studio 21.1.1.
Yes. Coeditor builds the cut inside Final Cut Pro in two ways. In Live mode you watch it cut and move clips with Final Cut's own commands, so every edit sits in the normal undo history. Instant mode makes the finished cut in one step, imports it as a new project and checks it against the plan.
Full answer on its own page
More
- You need: Accessibility permission for Coeditor, the FCP MCP Bridge extension window, macOS 15.6 or later and Final Cut Pro 12.x.
- Instant mode limits: one camera plus at most one synced screen recording, no separate audio file, no speed changes. Zooms and dissolves are written in Instant only.
- Already editing? "Connect an existing edit" lets you ask for small edits on an open timeline, without a story plan.
Not Coeditor. It never overwrites your timeline, and it keeps every earlier plan, so you can always go back. In Final Cut Pro its edits go into the normal undo history. In Premiere Pro and DaVinci Resolve it builds a new sequence or timeline and leaves yours alone.
Full answer on its own page
More
- Small edits after a build only touch timelines Coeditor built.
- Undo a plan in Coeditor at any time and build again.
- Final Cut Pro Instant mode imports the cut as a new project.
- Premiere Pro: use Edit > Undo for build steps. Resolve: scripting has no undo, but your own timeline was never touched.
Not with Coeditor. It builds the cut directly in your open Premiere Pro, DaVinci Resolve or Final Cut Pro project, so there's no XML file to export and import. There's no new app to learn and no export to round-trip. Your own timeline is left alone, and every keep and cut comes with a reason.
Full answer on its own page
More
How it reaches each editor:
- Premiere Pro: through the Premiere MCP Bridge panel. It builds a new sequence.
- DaVinci Resolve: through Resolve Studio's external scripting, set to Local. It builds a new timeline.
- Final Cut Pro: through the FCP MCP Bridge, in Live or Instant mode.
Because the cut is built in your real project, you finish it with your usual tools, effects and shortcuts.
Story, retention and how it decides
Coeditor reads the transcript and breaks it into story nodes: chunks of meaning with relations such as "sets up", "pays off" and "repeats". It then searches for a story plan that holds up against 90 cited storytelling rules. Every keep and every cut cites a rule, and the plan is validated before anything touches your timeline.
Full answer on its own page
More
Examples of what that looks like in a plan (illustrative):
- Cut: "Repeats n02. A second take of the same line." (
dss.primer-script.no-repetition)
- Cut: "A tangent. No later moment needs it." (
dss.p1.no-filler)
- Keep: "The payoff for n06." (
dss.summary.payoff-for-setup)
For the picture, Coeditor decides where to sample frames using how much the picture changes, the audio level and the word rate. The chat model can also look at still frames. A rule is still advice, not a hard constraint.
It can apply retention principles and show its working. Coeditor plans the cut against storytelling rules such as starting with an open loop that gives a reason to stay, giving every setup a payoff and not repeating points. A validated plan is advice, though, not proof that viewers will stay. You still judge the result.
Full answer on its own page
More
Rules from the catalogue it cites:
- "Start with an immediate open loop that gives a reason to stay."
- "Layer loops: one big loop resolved at the end, with smaller loops inside it."
- "Every kept setup needs a satisfying payoff."
- "Do not repeat points. The only exception is repetition that builds a motif."
The landing page's illustrative plan shows a loop re-opened before the next segment and a reaction moved to the front as a cold open. Each comes with its reason, so you can disagree.
Coeditor does. Every keep and every cut in its story plan comes with a short reason in plain words and the id of the storytelling rule behind it, for example "Repeats n02. A second take of the same line." You can read the reasoning before anything is built, change the plan in plain words, or undo it.
Full answer on its own page
More
- Reasons you can check: each one cites a rule from a catalogue of 90, paraphrased from the Dabi Systematic Storytelling course.
- Advice you approve: story advice items name their rule and only apply when you click Apply or say yes.
- Earlier plans: Coeditor keeps every earlier plan and never overwrites your timeline.
Coeditor's illustrative plan cuts a repeated take with the reason "Repeats n02. A second take of the same line." Its rules guide the plan rather than guarantee a cut. The rule behind it is simple: don't repeat points, unless the repetition builds a motif.
Full answer on its own page
More
- Repeated takes: story nodes can have a "repeats" relation; the no-repetition rule guides whether to cut them.
- False starts: Coeditor prefers a complete take over a false start that adds no meaning, and shows the reason.
- Review: check each cut's reason before you build, and undo the plan if it got it wrong.
Ask of each section: does it have a plot or emotional job, or does a later moment need it? If not, it's a tangent. That's the no-filler rule Coeditor applies, and each tangent it cuts is labelled with its reason, for example "A tangent. No later moment needs it."
Full answer on its own page
More
- The rule: "Every kept scene needs a plot or emotional function. Exposition is fine only when a later moment needs it."
- Keep what matters to you: say "Keep the part about pricing" and the plan changes.
- Check before you build: read each cut's reason, and undo the plan if you want the tangent back.
Coeditor uses 90 rules from the Dabi Systematic Storytelling course. Each rule is a short paraphrase of one course point, with its page or slide, and every keep and cut in a plan cites one. A rule is advice, not a hard constraint, and a validated plan does not prove the story works for viewers.
Full answer on its own page
More
Five rules from the catalogue:
- "Every kept setup needs a satisfying payoff." (
dss.summary.payoff-for-setup)
- "Every kept scene needs a plot or emotional function. Exposition is fine only when a later moment needs it." (
dss.p1.no-filler)
- "Start with an immediate open loop that gives a reason to stay." (
dss.primer-script.hook-reason-to-stay)
- "Layer loops: one big loop resolved at the end, with smaller loops inside it." (
dss.p2a.layered-loops)
- "Do not repeat points. The only exception is repetition that builds a motif." (
dss.primer-script.no-repetition)
Comparisons and alternatives
If you finish in Premiere Pro and want to stay there, Coeditor is one option. It plans the story with a reason for every keep and cut, then builds it as a new sequence in your open Premiere project. Descript is its own editor, so work made there comes back to Premiere through a timeline export.
Full answer on its own page
More
- Coeditor in Premiere: through the Premiere MCP Bridge panel. New sequence, main footage on V1 and A1, B-roll on V2. Your sequence is left alone.
- Story first: every keep and cut cites one of 90 storytelling rules.
- Also works in Final Cut Pro and DaVinci Resolve Studio.
- Limits: Coeditor is in private beta, Mac only, and can't undo inside Premiere (use Edit > Undo).
- Descript: its help says you can export your Descript timeline to Premiere Pro, Final Cut Pro, DaVinci Resolve, Pro Tools and more.
Sources: help.descript.com
Descript's help describes recording, editing and sharing in one app. Coeditor works inside the editor you already use: it builds a first cut planned around storytelling rules in Final Cut Pro, Premiere Pro or DaVinci Resolve, with a reason for every keep and cut.
Full answer on its own page
More
- Coeditor: no new app to learn and no export to round-trip. Each keep and cut shows the rule behind it.
- Coeditor limits: private beta, Mac only, with no Windows version, mobile app or screen recorder.
Sources: help.descript.com
Premiere's Text-Based Editing lets you cut by hand from a transcript. Coeditor proposes the whole story plan, with a reason and a rule for every keep and cut, then builds it as a new sequence in your open Premiere project. You can keep refining that sequence by hand afterwards, with Text-Based Editing or your usual tools.
Full answer on its own page
More
- Coeditor: decides what to keep and in what order, using story nodes and 90 storytelling rules.
- Text-Based Editing: Adobe's help says it transcribes your clips, and you use the transcript to select content and arrange a rough cut.
- Together: let Coeditor build the first cut, then tidy it by hand in Premiere.
- Coeditor limits in Premiere: zooms are centred only, and Coeditor can't undo inside Premiere (use Edit > Undo).
Sources: helpx.adobe.com