A director is an interactive Claude Code session, running the built-inDocumentation Index
Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
Use this file to discover all available pages before exploring further.
murmur-director agent persona with the Murmur MCP server attached. It is the recommended way to manage agents for any task that involves more than one agent or more than one step.
The director itself does not write code. It spawns autonomous agents, monitors them via mcp__murmur__status and mcp__murmur__ls, reviews the pull requests they open, and waits for your call to merge, follow up, or kill.
Start a director
murmur-director persona and the MCP server pre-wired. See murmur director for flags, including --persona to override the default.
What the director does
- Plans. Takes your goal, decides if it’s one task or many, picks a persona per piece, sequences dependencies.
- Spawns. Calls
mcp__murmur__spawnfor each piece. Parent and child relationships are preserved automatically. - Monitors. Events from agents (PR opens, CI results, child lifecycle, follow-ups) arrive on the director’s channel and surface to you in real time.
- Reviews. Runs
gh pr diffandgh pr checkson each PR, summarizes the change, and presents merge/rework recommendations. - Cleans up. Proposes killing completed agents after their PRs land.
Behavioral contract
Themurmur-director persona is constrained to make the director predictable as a coordinator:
- Questions stay read-only. If you ask “should we do X?”, the director answers. It does not spawn, edit, or merge. Discussion is not authorization.
- Destructive actions require an explicit imperative. Merge, kill, and close need a clear “do it” from you. The director will recommend; it will not act.
- Facts pass through unmodified. Specific facts you provide (error messages, IDs, config snippets) are forwarded to spawned agents verbatim, never paraphrased or filtered.
- The human is the quality gate. The director gates PRs against CI and presents its review. You decide what lands on
main.
When not to use a director
A director is overhead for a single, well-scoped task. For one-shot work, usemurmur spawn directly, or mcp__murmur__spawn from inside another agent’s session. The director’s value comes from the conversational loop across multiple agents; if the loop has one step, you don’t need it.
Related
| Type | Page |
|---|---|
| Reference | murmur director |
| Reference | mcp__murmur__spawn |
| Reference | mcp__murmur__status |
| Concept | Agent Personas |
| Concept | Agents |
| Concept | Events |
| Guide | Multi-agent orchestration |