Multi-agent control panel
See every AI agent session in one control panel. Tell parallel sessions apart, spot the one waiting on your approval, and stop it in one tap.
The control panel shows every agent session you run, on every machine, in one place. Two Claude Code windows, a Codex session and a background refactor each get their own row, so you can see which one is waiting on you, which is working, and which has failed. It lives at Dashboard > Agent, and agents can read the same view over MCP with list_sessions.
The blocked queue
Open pushary.com/dashboard/agent. The overview groups everything by session and puts the sessions waiting on you first.
- Board view sorts sessions into four columns: Working, Waiting on you, Done and Errored.
- List view shows each session as a card with its agent, machine, status and any open question.
You can answer a pending question right on the card, and Stop a session from it. Stopping works on every plan; see the kill switch. Without a paid plan, the overview shows 3 sessions.
Session status
Each session has a status computed from what it is doing now:
| Status | Meaning |
|---|---|
waiting | Has an open approval question. This is the one that needs you |
active | Seen in the last 2 minutes, nothing pending |
idle | Was active, but not seen for 2 minutes or more |
errored | Last reported an error |
offline | Not seen for 15 minutes or more |
waiting always wins: a session with a pending question shows as waiting however long ago it was last seen. errored stays until the session recovers or goes quiet for 15 minutes, when it shows as offline. Sessions not seen for 24 hours drop out of the dashboard.
How Pushary tells parallel sessions apart
The hook attaches two ids to everything a session sends:
Prop
Type
Site, agent type, machine and session together identify one session. That is why two claude windows in the same repo on the same machine show as two rows, and why a pending approval is pinned to the exact session that raised it.
The machine id is random, not derived from your computer. The CLI does send your computer's hostname when it registers the machine, so the dashboard and the phone app can show a name you recognize.
Start a session from your phone
The phone app can start a new agent session on a machine that runs the Pushary daemon. Install it as a background service with pushary daemon install; see the CLI reference.
The app accepts a launch only when the machine you picked, or at least one machine behind Any machine, is online and supports starting sessions remotely. It then shows the launch state: queued, claimed, retrying, started, failed or expired. A claimed launch holds a short lease, so if a daemon exits before it starts the process, another daemon can retry it, up to 3 attempts.
Current daemons confirm a launch only after the operating system creates the process. Older daemons still work, but the app cannot confirm their launches. It labels the result unconfirmed and suggests updating the CLI. Pushary never retries an unconfirmed launch, so it cannot start the same session twice.
Read sessions from an agent with list_sessions
A supervising agent can check the fleet over MCP. list_sessions is read-only: it never starts, stops or steers anything, and it sends no notification. It sees only your API key's site, and no parameter can widen it to another account.
{
"tool": "list_sessions",
"arguments": { "status": "waiting", "limit": 20 }
}It returns { sessions, pendingQuestions }. Each session carries its identity (agentType, agentName, machineId, sessionId), its computedStatus, its last action and event, and a readable timeAgo.
The status filter accepts active, idle, waiting and errored. It does not accept offline. An unfiltered call still returns offline sessions, but you cannot filter for them.
list_sessions needs a key from setup or the dashboard. Claude and ChatGPT connector keys cannot call it. See the tools reference for the full schema.
Next steps
Stop a runaway agent
Halt one session or every session from your phone or the dashboard.
See what already happened
The audit log keeps every question, approval and notification your agents sent.