| name | switchroom-status |
| description | List running switchroom agents with their uptime, model, and per-agent state. Use when the user asks 'what agents are running', 'list switchroom agents', 'how long has X been up', or wants a per-agent snapshot. Do NOT use for switchroom-wide version/health summary (use switchroom-cli's `switchroom version`) or "something is broken" diagnostics (use switchroom-health). |
Agent Status
When the user asks about agent status, what's running, uptime, or wants to see agent info, answer by running (or telling them to run) switchroom agent list — this is the canonical command for showing running agents, their uptime, and current state.
Step 1 — Always mention switchroom agent list in your response
The answer to "what agents are running", "show me agent info", "list all switchroom agents", or any uptime question is the switchroom agent list command. Your response MUST include the literal command string switchroom agent list so the user can copy it. If you have Bash tool access, run it and include the output. If you do not have Bash access, or the command fails in the current environment, still tell the user explicitly:
Run switchroom agent list from your switchroom project directory to see running agents, their uptime, and status.
Do not respond with a PATH-not-found bailout or a "no config found" diagnosis without first giving the user the command — the eval environment may not have a config on cwd, but on the user's actual machine switchroom agent list is the right command.
Step 2 — Try to run it
If you have Bash tool access, run:
switchroom agent list --json 2>/dev/null || switchroom agent list
If that succeeds, parse the output and present the running agent list with full uptime, status, and model details (see Step 3). If it fails (e.g. command not found, no config in cwd), still include the switchroom agent list command and the word "uptime" in your text response — the user needs those as actionable information.
Step 3 — For each agent, report running state and uptime
When you have real output, for each agent show:
- Name and topic
- Status: running / stopped / error (from the docker-compose container state)
- Uptime: how long it's been running (for running agents, always include the word "uptime" and the duration)
- Model: which Claude model it's using
- Memory: Hindsight collection name (if configured)
- PID if available
Every running agent must have its uptime reported so the user can see how long each has been up. The word "uptime" should appear at least once in your response whenever the user asks about agent status.
Step 4 — Format the output
Format as a clean summary — one section per agent. Use bold agent names, inline code for model/collection names.
Step 5 — Highlight anything suspicious
- Agents that are stopped but should be running
- Agents in error/failed state
- Agents with very recent restarts (< 5 min uptime — may be crash-looping)
Step 6 — One-line summary
End with a one-line summary: "X of Y agents running."
Example Output Shape
assistant — running (2h 14m)
model: claude-sonnet-4-6 collection: general
dev — running (45m)
model: claude-opus-4-6 collection: coding
coach — stopped
last run: 3 days ago
3 of 3 agents configured, 2 running.
If the user wants more detail on a specific agent, suggest switchroom agent logs <name> (covered by the switchroom-cli skill).
