Agents
opencode-squad registers a set of OpenCode agents for different kinds of work. Some are selectable as your current primary agent, some are hidden behind slash commands, and others are specialist subagents intended for delegated tasks.
Agent types
| Type | Page | How you use it |
|---|---|---|
| Primary agents | Primary agents | Select one as the current OpenCode agent for normal collaboration. |
| Slash-command agents | Slash-command agents | Invoke a hidden helper through commands such as /beta or /retitler. |
| Specialist subagents | Specialist subagents | Delegate focused work through OpenCode’s task mechanism or direct agent mention. |
| Council agents | Council agents | Ask for multi-perspective reasoning coordinated through the Council workflow. |
Names, display names, and routing keys
OpenCode shows agent display names in the UI, but squad.json model routing should prefer stable routing keys where they exist.
- Primary agents can change display names when
primary.personaandprimary.useRoleNameare configured, but their stable routing keys remainprimary/*. - Hidden command agents use short display names such as
beta,configuru, andretitler, while their stable routing keys aresquad/*. - Specialist subagents use their registry names directly, for example
codebase/analyzerorresearch/web-scout.
See Model routing for provider pools, workload handlers, and per-agent overrides.
Practical rule
Start with a primary agent. Use specialist subagents when the task has a narrow shape: codebase discovery, code review, web research, external repository analysis, or multi-agent reasoning. This keeps the primary conversation focused while still giving the work to a better-matched helper.