Muse Code CLI Headless Exec with PilotCut

The short version

Interactive Muse Code is muse in a project. For scripts and batch cleanup, Meta documents headless runs: muse exec "<prompt>" with META_API_KEY in the environment (auth, headless).

Point that agent at PilotCut's local MCP so batch work mutates a real .pcbundle: 83 purpose-built editing tools, shaped by tens of thousands of hours of video-editing practice, not Muse AI consumer tasks.

Muse Code remains BYO via MCP/CLI. It is not a PilotCut in-app catalog agent. PilotCut's featured agents are Claude Code, ChatGPT Codex, Grok Build, GitHub Copilot, OpenCode, Antigravity.

Install once, then exec

curl -fsSL https://dev.meta.ai/install.sh | sh
muse --version

Interactive auth once (browser or API key), or always supply the key for automation:

export META_API_KEY="<your-key>"

Per Meta, an environment API key takes priority over a stored browser session (auth).

Wire PilotCut MCP before unattended runs

Declare PilotCut in Muse mcp_servers (stdio or streamable_http) while the PilotCut editor window that owns the .pcbundle is open (MCP).

PilotCut's Core Agent chat panel gates on riskTier. Muse Code as a third-party MCP client does not get that gate. Prefer prompts that demand confirm:false plans first on silence/filler tools, then an explicit second step for confirm:true.

Example headless shapes

META_API_KEY="$MUSE_KEY" muse exec \
  "On the open PilotCut .pcbundle, run edit-words cutSilences and removeDeadAir with confirm:false only. Print the plan. Do not apply."

META_API_KEY="$MUSE_KEY" muse exec --json \
  "Apply the reviewed silence plan with confirm:true, then export type=fcpxml to the path I specify."

muse exec --prompt-file ./pilotcut-batch-task.txt

Meta's exit codes reflect how the run ended, not whether the edit is correct (0 turn complete, 1 fail/cancel, 2 usage error). Gate on your own checks after the run (headless).

Optional: --max-model-steps caps a stuck loop. Resume with muse exec --session-id <uuid> "Continue." when you need a follow-up turn.

What batch cleanup is good for

• Propose breath-safe silence / filler plans across talking-head takes
• Re-run the same prompt file after human review of the plan
• Write export type=fcpxml when the next stop is Final Cut

It is not text-to-video. It is not Muse AI. It is a coding agent calling PilotCut tools on local media.

Eligibility and pricing

Meta positions Muse Spark 1.2 with expanded global access in Muse Code / Model API. Verify account eligibility at auth. Check Meta's live pricing pages for dollars. PilotCut stays free during beta with no editor-side credit meter for BYO agent edits.

Facts (checked 2026-09-15)

Also read

• How to use Muse Code with PilotCut MCP
• How to use Claude Code / ChatGPT Codex MCP/CLI without Resolve Studio
• Edit videos with AI agents

Bottom line

Use muse exec + META_API_KEY for batch propose/apply loops on a .pcbundle, with Meta's sandbox and MCP warnings respected. Muse Code stays BYO outside the featured catalog list. Keep the cut on PilotCut's local timeline.

Try PilotCut. Free during beta. Bring the agent you already pay for.