Resolve Studio Control
01 / START
Health before action
Confirm Python 3.11, Resolve 21 and the installed bridge. Open a saved project, launch Workspace → Scripts → Codex Resolve Bridge, then ask Codex to run resolve_health.
Studio support / v0.2.1
Keep the room moving.
A short, production-minded path from first install to a clean Resolve handoff. If the bridge is not healthy, stop before editing.
02 / DELIVERY
Use the protected loop
Preflight, export a unique DRP backup, duplicate a versioned timeline, edit only that revision, preflight again, render, and verify the output with QC.
03 / REPORT
Send evidence, not secrets
Include Resolve version, transport, stable error code and request ID. Redact project paths, media, tokens and private audit details before sharing.
Fast diagnosis
Common stops, clear next moves.
The connector fails closed when a path, confirmation, or delivery gate is unsafe.
Scripts shows “No Scripts”Restart Resolve after installation, open a saved project, then check Workspace → Scripts.bridge_not_runningLaunch Codex Resolve Bridge from Workspace. Keep it on 127.0.0.1; never enable network scripting.direct_unavailableExpected on Resolve Lite. Leave DAVINCI_TRANSPORT=auto enabled for signed loopback transport.render_setting_rejectedDiscover exact format and codec tokens with resolve_get_render_options before configuring the render.unsafe_pathUse a canonical configured media/output root. Symlink escapes and overwrites are refused by design.Need a human review?