Multi Doctor
Multi Doctor is a built-in agent that ships with Multi. You select it directly from the agent picker - it appears under Built-in alongside Quick and Autonomy - and use it like any other agent: just describe what you want, and it does the work.
Using Multi Doctor to improve Multi’s capabilities
What it does
Section titled “What it does”Multi Doctor authors and repairs Multi’s own configuration. Its scope is exactly five artifacts:
- Custom agents -
.multi/agents/*.md(project) or~/.multi/agents/*.md(global) - Skills -
.multi/skills/<name>/SKILL.md(project) or~/.multi/skills/<name>/SKILL.md(global) - Personas -
~/.multi/soul/<name>.md - AGENTS.md - repo root, or
~/.multi/AGENTS.mdas a global fallback .multiignore- repo root, using gitignore syntax
Boundaries
Section titled “Boundaries”- It only touches those five artifacts.
- It never runs destructive commands.
- It won’t create unsolicited summary files.
Example prompts
Section titled “Example prompts”Select Multi Doctor from the agent picker and paste one of these:
- “Create a custom agent that reviews my React components for accessibility issues.”
- “Create a skill that captures our database migration workflow so agents follow it every time.”
- “My skill isn’t loading when I ask for it - diagnose why and fix it.”
- “Add a persona that keeps answers short and blunt.”
- “Set up a
.multiignorethat hides my.envfiles and deploy keys.” - “My custom agent isn’t showing up in the picker - figure out why.”
Related
Section titled “Related”- Custom Agents - the file-based agents Multi Doctor authors and repairs
- Skills - reusable guidance Multi Doctor can author and repair
- Personas - customize Multi’s identity and communication style
- AGENTS.md - project-wide guidance for every agent
- Ignoring Files - steer Multi away from sensitive paths with
.multiignore