Built-in agents
buildThe default agent. It runs tools under the permission rules.planRead-only planning on the strongest tier. Label: Deep Plan.plan-quickThe same planning flow on the cheapest tier. Label: Quick Plan.exploreA subagent for fast codebase search and reading.generalA subagent for research and multi-step work in parallel.
Use /agents inside a session to switch, or start with --agent. The default can be set with default_agent in config.
Subagents
A primary agent can hand part of the work to a subagent. This is how Midas runs several tasks in parallel without mixing their context. Nesting defaults to one level; set it with subagent_depth.
Create an agent
midas agent createThe command writes a Markdown file in the project or global config. You can write one by hand instead. The file name is the agent name, the body is the system prompt, and the frontmatter sets the behavior:
---
description: Review migrations for data loss
mode: subagent
model: provider/model
permission:
edit: deny
---
You review database migrations. Flag any migration that drops a
column, rewrites a table, or cannot be rolled back.Agents live in .midas/agents/ or ~/.config/midas/agents/. The mode is primary, subagent, or all.
Override a built-in
A custom agent with the same name merges its fields into the built-in agent. Set disable: true to remove a built-in. A team can use this to tighten the build agent or replace the default planner without changing the code.
Related
- Plan mode covers the two planners.
- Permissions covers the permission block.
- Skills attaches a workflow to an agent as a slash command.