Configuration
Multi can be configured at three different layers, each with a clear purpose:
| Feature | Scope | Purpose |
|---|---|---|
| Personas | Global (user) | Identity and communication style |
| AGENTS.md | Workspace | Project-specific build, test, style, and workflow instructions |
| Skills | Workspace or user | Reusable, activatable workflows loaded on demand |
Communication Style with Personas
Section titled “Communication Style with Personas”Customize Multi’s personality and communication style with Personas. Personas live in ~/.multi/soul/ and affect how Multi expresses itself - not its capabilities or available tools.
Manage personas from the Multi panel → Settings (gear icon) → Personas. See the Personas guide for details.
Project Context with AGENTS.md
Section titled “Project Context with AGENTS.md”For project-specific instructions - build commands, code style, testing conventions, and other context Multi needs to work effectively in a repository - add an AGENTS.md file at the root of your project.
Multi loads a single AGENTS.md from the workspace root - there’s no global override and nested files are not traversed.
See the AGENTS.md reference for details and examples.
Reusable Workflows with Skills
Section titled “Reusable Workflows with Skills”For focused, reusable workflows you want Multi to activate on demand - code reviews, refactoring playbooks, deployment checklists, team conventions - use Skills.
Skills live in .multi/skills/ or .agents/skills/ (project) or ~/.multi/skills/ or ~/.agents/skills/ (user) and are loaded into the agent context when activated. See the Skills guide to learn how to create one.