Agent Profiles
How Andromity's builder, coder, planner and reviewer profiles change what the coding agent does and which tools it can use, and how to switch between them.
A profile sets how Andromity approaches a task and which of its tools it gets. The permission mode then decides which of those actions need your approval.
| Profile | Use it to | Edits files and runs commands |
|---|---|---|
| builder (default) | Build features and larger changes; plans first when a change is complex | Yes |
| coder | Make focused changes quickly, without planning | Yes |
| planner | Design a change and write a plan, without touching code | No |
| reviewer | Audit code for bugs and security issues, without changing it | No |
builder
The default. For a small change in one file, builder makes the change directly. For complex work (several files, architecture, multi-step changes) it writes a structured plan first and asks clarifying questions when something is unclear. In SAFE and TRUST it waits for you to approve the plan; in FULL and YOLO plans are approved automatically.
Tools: read, search and list files; write and edit files; run commands and background processes; plans; clarifying questions; web search and URL fetch; subagents; session collaboration tools.
coder
A fast, direct implementer. It reads a file before editing it, prefers batching edits, and ends with a short summary. If a change spans three or more files or needs architectural decisions, it suggests switching to builder.
Tools: everything builder has except plans, clarifying questions and subagents.
planner
Plans without editing code. When requirements are unclear it asks one to three focused questions, then writes a plan with an overview, goals and non-goals, architecture, file-by-file changes, risks and edge cases, and a testing plan. To carry out the plan, switch to builder or coder.
Tools: read, search and list files; plans; clarifying questions; subagents; session tools for reading messages, asking questions and handoffs. No web tools, file edits or commands.
reviewer
Read-only review. It looks for security issues (SQL injection, XSS, CSRF, remote code execution), logic flaws, edge cases, performance problems and anti-patterns, tags findings by severity (CRITICAL, HIGH, MED, LOW), points out missing tests, and recommends fixes without applying them.
Tools: read, search and list files; web search and URL fetch; reading session messages and shared state. No plans, subagents, file edits or commands.
Hard limits for planner and reviewer
Planner and reviewer are refused write_file, edit_file, edit_file_multi, shell_exec, shell_bg and shell_kill in every permission mode, including FULL and YOLO. Subagents they start lose those tools as well.
MCP tools are offered to every profile through a tool catalog the agent can look up; the restrictions above apply to Andromity's own file and command tools.
Subagents
A subagent uses its parent's profile and permission mode. Subagents cannot start further subagents, and a subagent started from planner or reviewer, or in an untrusted folder, has no file-editing or command tools.
Switching profiles
- VS Code chat: the profile menu under the prompt box (Builder, Coder, Planner, Reviewer). The change applies from the next turn.
- Andromity Hub: Preferences → Agent Profile.
- Terminal app:
/profile <name>,/profilefor a picker, or Ctrl+U. - Config file:
profileunder[default]inconfig.toml.
[default]
profile = "builder"Permission Modes
What SAFE, TRUST, FULL and YOLO let the Andromity coding agent do without asking, what always needs your approval, and how to switch modes in VS Code, the terminal and config.toml.
Skills
Teach Andromity reusable workflows with SKILL.md skills. Skill format, where skills are discovered, how the agent loads them, installing from the catalog, mentioning skills in chat, and how folder trust applies.