MiMo Code comes with three built-in modes (primary agents), each with a distinct role:
build — default primary agent with full tool access for general development work.plan — restricted primary agent for read-only analysis and planning.compose — primary agent that orchestrates work through built-in skills.There are also general / explore — subagents invoked by primary agents for delegated tasks.
compose is a verb form, matching the build/plan/explore naming convention. It does not replace build; it complements it by adding a workflow-aware mode where the model is encouraged to think in terms of named, reusable skills rather than ad-hoc procedures.
Build is the default mode with all tools enabled. This is the standard mode for development work where you need full access to file operations and system commands.
A restricted mode designed for planning and analysis. In plan mode, the following tools are disabled by default:
write - Cannot create new filesedit - Cannot modify existing files, except for files located at .mimocode/plans/*.md to detail the plan itselfpatch - Cannot apply patchesbash - Cannot execute shell commandsThis mode is useful when you want the AI to analyze code, suggest changes, or create plans without making any actual modifications to your codebase.
Compose is a primary agent in MiMo Code that orchestrates task execution through a curated set of built-in skills. Instead of relying on a single monolithic prompt, Compose consults a library of 13 focused skills—covering testing, debugging, planning, collaboration, and meta-development—and selects the right skill for each step of your workflow.
Switch to the Compose agent when you want a workflow-driven loop: brainstorm a feature, write a plan, execute it with TDD, verify before completion, and request a code review—all guided by skills.
Compose was inspired by the open-source superpowers workflow and ported into MiMo Code as a first-class primary agent. Like build and plan, Compose handles your main conversation and can be selected with the Tab key. What sets it apart is the bundled skill library: every skill ships with the binary, is loaded at runtime under the compose: namespace, and is available only when the Compose agent is active.
Compose is registered as a built-in primary agent under the name compose. To activate it:
switch_agent keybind) to cycle through primary agents until Compose is selected.@compose in a message.No additional configuration is required. The skill bundle is extracted to {data}/compose/{version}/ on first use and kept up to date across MiMo Code releases.
Compose ships with 13 skills, grouped by category. They are referenced from the model side via the compose:<short-name> namespace.
| Skill | Purpose |
|---|---|
compose:tdd | Test-driven development workflow |
| Skill | Purpose |
|---|---|
compose:debug | Systematic debugging methodology |
compose:verify | Verification before completion |
| Skill | Purpose |
|---|---|
compose:brainstorm | Brainstorming with the user |
compose:plan | Writing implementation plans |
compose:execute | Executing an approved plan |
compose:parallel | Dispatching parallel agents |
compose:review | Requesting a code review |
compose:feedback | Receiving and applying review feedback |
compose:worktree | Working in a git worktree |
compose:merge | Finishing a development branch |
compose:subagent | Subagent-driven development |
| Skill | Purpose |
|---|---|
compose:new-skill | Authoring a new skill |
You can switch between modes during a session using the Tab key. Or your configured switch_mode keybind.
See also: Formatters for information about code formatting configuration.