Routes
/agents— list all agents/agents/:id— agent detail page/agents/:id/edit— agent editor/agents/:id/workspace— workspace manager (covered on its own page)
Backing RPC
The list, detail, and editor are powered by:agents.list— list viewagents.get— detail pageagents.create,agents.update,agents.delete— editor and delete actionsagents.suspend,agents.resume— status actionsagent.getOperationModels— shows the resolved primary model and per-operation overrides
persistToConfig (writes agents.<id> into config.yaml, then schedules a daemon restart).
What You See
The Agents view has three sub-views: a list of all agents, a detail page for each agent, and an editor for changing agent settings.Agent List
The main view is a sortable data grid showing every configured agent. Click any column header to sort by that column (the Actions column is not sortable). The columns are:
Each agent’s status appears as a colored tag:
- Active (green) — The agent is running and processing messages
- Idle (blue) — The agent is running but has had no recent activity
- Suspended (yellow) — The agent has been paused by a user
- Error (red) — Something went wrong and the agent needs attention
Agent Detail
The detail page gives you a comprehensive look at a single agent. At the top, a breadcrumb trail lets you navigate back to the agent list. Stat cards across the top show at-a-glance numbers:- Messages handled today
- Tokens used (input and output combined)
- Tool calls made
- Configuration summary — The agent’s provider, model, max steps, and other core settings displayed in a two-column grid
- Budget usage — Visual progress bars showing how much of the agent’s per-execution, per-hour, and per-day token budgets have been consumed
- Circuit breaker status — Whether the circuit breaker is closed (normal), open (tripped due to errors), or half-open (testing after a cooldown)
- Safety config — Context guard settings and SDK retry configuration
- Skills list — All skills and tools available to this agent
- Routing bindings — Which channels and routing rules direct messages to this agent
Agent Editor
The editor organizes agent settings into 13 sections using an accordion layout. The first section is always visible; the remaining 12 are collapsible:Sections marked (System-Wide) affect all agents, not just the one being edited. Changes to these sections are applied globally.
Common Tasks
View Agent Details
1
Open the Agents view
Click Agents in the sidebar.
2
Click an agent row
Click on any agent in the list to open its detail page with stats, configuration, and available actions.
Suspend an Agent
1
Find the agent
In the agent list, locate the agent you want to suspend. You can also open the agent detail page.
2
Click Suspend
Click the Suspend button. The agent immediately stops processing new messages. Its status tag changes to yellow.
3
Resume when ready
To restart the agent, click the Resume button that replaces the Suspend button. The agent goes back to processing messages.
Edit Agent Configuration
1
Open the agent detail page
Click the agent row in the list to open its detail page.
2
Click Edit
Click the Edit button in the header to open the agent editor.
3
Make your changes
Expand the accordion sections to find the settings you want to change. Modify the fields as needed.
4
Save
Click Save to apply your changes. A confirmation message appears if the save succeeds.
Delete an Agent
1
Open the agent detail or list
Navigate to the agent you want to remove.
2
Click Delete
Click the Delete button. A confirmation dialog appears asking you to confirm.
3
Confirm deletion
Click Confirm in the dialog to permanently remove the agent.
Open the Workspace Manager
1
Open the agent detail page
Click the agent row in the list to open its detail page.
2
Click Workspace
Click the Workspace button in the header. This opens the workspace manager for that agent, where you can browse files, edit content, and manage git history.
About the circuit breaker: If an agent hits too many consecutive errors, the circuit breaker trips to prevent runaway costs. While open, the agent stops making AI provider calls. After a cooldown period, it enters a “half-open” state where it tests with a single request. If the test succeeds, the circuit breaker closes and the agent resumes normal operation.
Related Pages
Chat Console
Start a conversation with any of your agents.
Sessions View
Browse conversation histories for all agents.
Agents Documentation
Learn about agent configuration, routing, and behavior in depth.
Workspace Manager
Browse and edit workspace files, manage git history.
