DaVinci Resolve Studio 21.1 AI Assistant Not Working: Codex Opens Claude (Fix + PilotCut)

DaVinci Resolve Studio 21.1 adds a native MCP path and File > Setup AI Assistants for Claude, Claude Code, and ChatGPT Codex (CineD; Blackmagic Studio materials). That feature is Studio-only. The same release moved Python scripting out of free Resolve (CineD).

Here is a specific setup problem: you pick ChatGPT Codex, but Claude or Claude Code opens instead.

What that symptom usually means

Treat "Codex opens Claude" as setup and routing confusion, not as a confirmed Blackmagic defect. We found no public bug report for it. Common causes when multiple assistants are registered:

1. The wrong assistant is still marked connected in File > Setup AI Assistants.
2. List order or the last successful handshake becomes the effective handler.
3. You reconnect the wrong client after a quit or update.
4. Another assistant app still owns the protocol handler on the Mac.
5. ChatGPT Codex is not installed, not signed in, or Resolve was not restarted after a reconnect.

These are troubleshooting steps, not a confirmed root cause.

Fix checklist inside Resolve

Work through this calmly:

1. Open File > Setup AI Assistants.
2. Read which assistants show as connected. Disconnect anything you do not want for this session.
3. Disconnect and reconnect the ChatGPT Codex client you intend to use.
4. Confirm the ChatGPT Codex app or CLI is installed and signed in.
5. Quit other assistants that may have stolen the protocol handler (Claude desktop, Claude Code sessions fighting for the same slot).
6. Quit Resolve fully, reopen the project, and test the assistant entry again.
7. If a third-party MCP bridge is also running, pause it so you are not mixing native Setup AI Assistants with a second server.

If the wrong client still launches, re-check the Setup list before assuming the NLE itself is broken.

Studio gate and community MCP

Native AI Assistants are a Studio feature. Free Resolve users who relied on Python scripting lost that path in 21.1 (CineD).

Community MCP such as samuelgursky/davinci-resolve-mcp is a different stack. Install docs still expect DaVinci Resolve Studio and Preferences > General > External scripting using = Local. That preference path is fragile for many creator workflows. It is not a substitute for fixing Setup AI Assistants routing when you already paid for Studio.

Blackmagic lists Studio at about $295 one-time (taxes and regional pricing vary; checked 2026-09-08). You still bring your own agent subscription on top.

When PilotCut is the lighter path

Use PilotCut when the weekly job is Mac-local creator cleanup and the friction is assistant routing, External scripting Local, or full-NLE weight for a demo timeline.

PilotCut facts:

• Free during beta. Bring the agent you already pay for.
• Local-first Mac timeline. Media and project stay on your Mac.
• Same 83 purpose-built editing tools for UI and agent.
• Agents: Claude Code, ChatGPT Codex, Grok Build, GitHub Copilot, OpenCode, Antigravity.
• Propose then commit on the named confirm-capable actions. The Core Agent chat panel can gate on risk tiers. CLI and third-party MCP clients are not gated the same way.
• Final Cut handoff: export type=fcpxml writes FCPXML 1.11 with absolute media paths.

No Studio seat required for the agent path.

Also read

• Resolve Studio 21.1 native MCP vs PilotCut
• Resolve Studio 21.1 MCP API gaps vs PilotCut
• How to use Claude / Codex MCP without Resolve Studio
• Best free DaVinci Resolve Studio alternatives

Bottom line

If ChatGPT Codex opens Claude in Resolve Studio 21.1, start in File > Setup AI Assistants. Disconnect, reconnect the Codex client, quit competing assistants, confirm sign-in, and restart Resolve.

If that stack still costs more friction than the edit is worth, try PilotCut for local Mac agent cleanup without a Resolve Studio license.

Try PilotCut. Free during beta.