Managing Agents

Click any agent to open its detail page. The page lands on the Overview tab and organizes everything else into tabs:

Tabs marked owners only are hidden from users an agent is merely shared with, and are never shown on the system agent. Dashboard, Brain, Git, and A2A appear only when that agent or instance supports them.

Every visible tab is deep-linkable with ?tab= — including the conditional ones. A ?tab= value naming a tab you cannot see falls back to Overview. Two legacy links still resolve: ?tab=guardrails opens Settings, and ?tab=session redirects to that agent's Workspace conversation.

When the window is too narrow to fit every tab, the trailing tabs collapse into a More ▾ menu at the end of the tab strip. If the active tab is inside the menu, the More button carries the active highlight. Deep links via ?tab= work either way.

The Overview tab is a glanceable, database-backed summary. It renders even when the agent is stopped:

The persistent header above the tabs still owns live “now” state: status, CPU/memory gauges, cost, and quick controls. The Overview shows trends; the header shows the present.

Toggle an agent between Running and Stopped using the switch on the Dashboard, Agents page, or Agent Detail page. A loading spinner displays during state transitions.

The display label is the friendly name shown across the UI — the header, agent pickers, search, sort, and the activity timeline. Editing it is the everyday “rename”: it changes what people read without moving the immutable slug (name), so it never breaks URLs, MCP tool names, schedules, or webhooks. For most day-to-day relabeling, this is the change you want; the heavier Rename below moves the slug itself.

Renaming moves the immutable slug itself — the heavier operation. Because the slug is what URLs, MCP tool names, schedules, and webhooks resolve to, prefer the Display Label above when you only need to change the friendly name.

Click the pencil icon next to the agent name on the Agent Detail page to edit inline. Renaming is atomic: it updates the database, renames the Docker container, and broadcasts the change via WebSocket.

Restrictions: system agents cannot be renamed. Only owners and admins have permission to rename.

Use the Delete button on the Agent Detail page. A confirmation dialog is required. Deletion cleans up the container, network, sharing records, schedules, activities, and event subscriptions.

The agent header displays status (Running/Stopped), CPU and memory usage, network I/O, and uptime. Telemetry auto-refreshes every 10 seconds.

Fleet-wide monitoring is available at GET /api/monitoring/fleet-health. Health levels, from best to worst: healthy, degraded, unhealthy, critical, unknown.

Configure per-agent memory and CPU limits from the agent header: click the gear button (“Configure resources”) to open the resource modal. Limits are enforced at the container level and take effect on the next restart — see Agent Configuration for valid values and fleet-wide defaults.

Execution timeout is configurable per agent (range: 60–7200 seconds, default: 3600 seconds / 60 minutes).

The agent's timeout is the ceiling for any of its schedules — setting it below an active schedule's timeout_seconds is rejected with 400 error=agent_timeout_below_active_schedules.

The Agents page shows horizontal row tiles with success rate bars. Filter by name, status, or tags. The Dashboard offers a network graph view and a timeline view.