Skip to main content
Starts an interactive director session. It fetches a persona from the catalog, connects the Murmur MCP server, and launches Claude Code. Pass --backend codex to launch Codex instead. The resulting coding session can spawn and coordinate agents through conversation. murmur director owns four flags: which backend to launch, which persona to install, whether the session receives event pushes, and which session to open. Every other flag belongs to the backend, and you pass it through after a bare --.

​
Synopsis

​
Prerequisites

The command checks three things before starting the session: the backend is installed, the murmur MCP server is configured for it, and it is authenticated: If any prerequisite is missing, the command exits with a message telling you exactly what to run.

Why murmur director passes --dangerously-load-development-channels

By default, murmur director launches Claude Code with --dangerously-load-development-channels server:murmur. The flag opts the session into Claude Code’s channel transport, which Murmur uses to stream real-time events (PR comments, CI results, child lifecycle, follow-ups) from the control plane into your conversation as <channel> tags. Without it the director can’t receive event pushes, and the coordinator loop across multiple agents stops working.The dangerously- prefix is Claude Code’s wording for an opt-in developer feature, not a security warning specific to Murmur. The same flag is also used by murmur init and by every interactive agent VM that Murmur spawns, so all sessions can post to and receive from server:murmur.When Claude Code prompts you to confirm channels, say yes and opt in. Murmur can’t deliver event pushes without it.Pass --channels=false for a session that runs without the channel transport. Use it when you want a director-persona conversation that is not driven by incoming events. Codex has no channel transport, so Codex sessions never receive event pushes; asking for them with --channels there fails rather than opening a session you would wrongly believe is wired up.

​
Arguments

​
Passing flags to the backend

Director declares only its own four flags. Anything else goes after a bare -- and reaches the backend untouched, so the backend’s whole surface is available without Murmur redeclaring it:
Run claude --help or codex --help for what each accepts. Two kinds of argument are refused rather than forwarded, because they would override a decision the director has already made:
  • The persona, and on Claude the session’s display name. Director installs the catalog persona itself, and both backends resolve a repeated option to its last occurrence, so a forwarded copy would replace it, leaving a session that reports itself as a director while running a different prompt. On Claude that covers --append-system-prompt and --name/-n, the display name director sets from the persona. On Codex, where director sets no session name, it is a developer_instructions assignment passed through -c/--config.
  • Session selection. Director opens the session you named with --resume. A second selector on the command line would put the backend’s precedence rules, rather than what you typed, in charge of which session opens. On Claude that covers --resume/-r, --continue/-c and --from-pr; on Codex, the resume and fork subcommands and --last.
A flag director does not declare is an error when written before the --, so a typo fails instead of reaching the backend as an argument you did not intend.

​
Resuming a session

Neither backend persists the persona. Claude Code’s appended system prompt lasts only for its current run, and Codex’s developer instructions are scoped to one invocation. A resumed director session therefore fetches the persona from the catalog and installs it again. The --resume option requires Murmur configuration and API access; a local session file alone is insufficient.

​
Examples

​
Start a director session with the default persona

Fetches the murmur-director persona, then opens an interactive Claude Code session with the murmur MCP server attached. You land in a conversational interface where you can give instructions, spawn agents, check status, and coordinate work.

​
Start a session with a custom persona

Fetches the code-reviewer persona from the catalog and starts the session with that persona’s prompt.

​
Continue a previous session

The first opens the backend’s session picker; the second opens that session directly.

​
Start a session on Codex

Installs the persona as Codex developer instructions and launches Codex with the murmur MCP server attached. Director starts Codex with --sandbox danger-full-access --ask-for-approval on-request.

​
Start a session without event pushes

Opens a director session with the persona and MCP server, and no channel transport, so no event pushes arrive in the conversation.

​
Errors

  • Director, concept overview of what a director is and the behavioral contract it follows
  • Agent Personas, what personas are and how they shape agent behavior
  • Catalog, where personas and other resources live
  • Agents, concept overview
  • Events, what arrives on the channel transport
  • murmur status, check agent status during a director session
  • Multi-agent orchestration, guide to coordinating agents as a director