Documentation Index
Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
Use this file to discover all available pages before exploring further.
An agent persona is a reusable template for how an agent should think and what tools it should use. It’s the difference between spawning “a Claude” and spawning “a code reviewer” or “an architect drafting a proposal” — same model underneath, different instructions, tool budgets, and behavior.
Personas live in the catalog as the agent-persona kind. They are tenant-scoped, version-controlled, and authored in Markdown with YAML frontmatter or as structured YAML.
What a persona contains
| Field | Purpose | Example |
|---|
name | DNS-label identifier within the tenant | programmer |
description | One-line summary shown in the spawn UI | ”Mythical programmer obsessed with code quality” |
prompt (body) | The system prompt — instructions, voice, principles | (markdown prose) |
model | Override the default model | claude-opus-4-7 |
tools | Allowlist of Claude Code tools the agent may use | Bash, Edit, Read, Grep |
disallowedTools | Tools the agent may not use | NotebookEdit |
maxTurns | Maximum number of turns before the agent stops | 50 |
tasks | Default checklist items with optional activation conditions | (see reference) |
The prompt is the heart of the persona. Write it as you would a senior engineer’s briefing: principles, conventions, what to avoid, what to prefer.
Built-in personas
Murmur ships platform-managed personas that exist in every tenant:
| Persona | Optimized for |
|---|
programmer | Implementation, code review, simplification |
architect | Design docs, proposals, package boundaries |
designer | UX, visual polish, dashboard work |
researcher | Investigation, fact-checking, root-cause |
tester | Test strategy, flake fixing, integration tests |
frontend | React/TypeScript SPA work |
director | Spawning + coordinating other agents |
Use them via the --agent flag on murmur spawn, or select them in the dashboard’s spawn dialog.
Authoring your own
Create personas with murmur set agent-persona — either piping a Markdown file with YAML frontmatter, or structured YAML. Both produce identical catalog records. See the agent-persona reference for all fields and formats.
Lifecycle
The agent inherits the persona’s tools, model, and system prompt at spawn time. Edits to personas affect future spawns only — running agents continue with the persona they were spawned with.