Subagents
Prepare specialist assistants for independent subtasks. The main task owns the goal, delegation, and synthesis; each subagent owns a clearly defined part.
When to use one
Useful subtasks include checking sources, reviewing a set of files, or researching one topic with clear inputs and outputs. Short questions rarely need delegation. Several assistants editing the same file can introduce conflicts.
Give a subtask a clear role
Source checker
Independently check evidence. The main task decides how to update the document.
- Input
- Text and permitted sources
- Output
- Supported, unconfirmed, and incorrect claims
- Boundary
- Read only; do not edit the text
Create a specialist
- Open Subagents in Extensions and choose Add.
- Enter a name and description explaining its specialty and when to use it.
- Write instructions covering input, deliverable, and stop conditions.
- Configure model, runner, and tools using the available fields.
- Save, check its status, and try it on a small task.
Definitions are Markdown files, stored by default in ~/.evox/agent/agents/; the management page shows the directory it reads. Frontmatter holds the name, description, model, runner, and tool configuration; the body holds the instructions. The management UI exposes validation status and errors.
Name and description are required. A blank model inherits the model; a blank tool list inherits all tools, rather than disabling them. For a read-only assistant, name the permitted reading tools and constrain its instructions. Deleting a definition removes the assistant file; it does not undo earlier edits or external operations.
Example: a source checker
| Field | Example |
|---|---|
| Name | Source checker |
| Description | Verify claims in product documentation |
| Input | Text to check and permitted sources |
| Output | Supported, unconfirmed, and incorrect claims, with sources |
| Boundary | Read only; do not edit the article or send messages |
An instruction might be: “Check each claim using only the permitted sources. Mark unsupported claims as unconfirmed. Return a concise verification table.”
Inspect status
| Status | Action |
|---|---|
| Active | Definition is recognized; verify actual usability with a task |
| Shadowed | Check duplicate names or precedence to identify the effective definition |
| Invalid | Fix the reported missing name, description, or file format |
A listed definition is not necessarily running. Assign a clear subtask and inspect its result rather than only its name.
Synthesis and permissions
Give assistants separate materials or questions. Let the main task combine results and resolve disagreements. Tool selection and execution authorization are separate; selecting a tool does not approve all its actions.
Subagents also differ from cross-device swarm collaboration. One defines specialized roles; the other involves device connectivity and delegation. See Using swarm.
Next: Permissions and approvals · MCP servers