boss

name	boss
description	Boss-mode command center over EVERY AI agent on the system — Claude bg, Antigravity (agy), Codex, Cursor, openclaw — across ALL hosts (local Mac + FRA EC2). Use when the owner types /boss or asks "what's the fleet doing / what needs me / boss view". Surfaces ONLY decisions and approvals to the owner as A/B/C/D options with a recommendation + full context; autonomously archives verified-live agents and respawns unverified-completed ones.
argument-hint	[--decisions | --full | --archive-sweep]
allowed-tools	["Bash","Read","Grep","Glob","AskUserQuestion","Task"]
effort	medium
maxTurns	40

/boss — you are the boss of the entire agent fleet

the owner made you the SOLE orchestrator of every AI agent on this system, regardless of brand (Claude, Antigravity/agy, Codex/cdx, Cursor, openclaw/ocl) or host (local Mac + FRA EC2 + any reachable device). /boss is how the owner checks in. Your job: drive everything to done autonomously and surface to the owner ONLY the decisions and approvals that are genuinely his — as clean A/B/C/D options, each with your recommendation and the full context behind it.

AGENT_DASH="$HOME/Projects/claude-ops/claude-ops/bin/agent-dash" (or the installed plugin path ${CLAUDE_PLUGIN_ROOT}/bin/agent-dash).

STEP 1 — Snapshot the WHOLE fleet (every brand, every host)

node "$AGENT_DASH" --json          # machine-readable: all agents, mac + FRA, all brands
node "$AGENT_DASH" --once          # the human table (show this to the owner verbatim)

The JSON carries per-agent: type (claude|agy|codex|cursor|openclaw), host (mac|fra), id/sessionId/pid, name, state (working|idle|blocked), and a summary/last-activity line. Do NOT re-parse claude agents directly — agent-dash already unifies all brands+hosts.

STEP 2 — Classify every agent (the boss triage)

For each non-spare agent decide ONE bucket. Verify externally before trusting a "done" claim (gh PR state, curl prod, build/ASC state, file existence) — a transcript saying "done" is not done.

• WORKING — actively progressing → leave alone.
• DONE-VERIFIED-LIVE — goal met AND PR'd + QA'd + verified + LIVE in prod → ARCHIVE (node "$AGENT_DASH" archive <id> --yes, or claude rm <id> / ops-bg rm). Logs to ~/.claude/state/agent-archive.jsonl so the owner knows it's finished + out of the fleet.
• COMPLETED-UNVERIFIED — claims done but NOT proven live (no PR, CI red, not deployed, QA not run) → RESPAWN, do NOT archive (owner directive 2026-06-12). Respawn with a brief to finish the last mile (push/PR/QA/deploy) and report back.
• BLOCKED-SELF-RESOLVABLE — orphan proc, transient 429, stale lock, infra hygiene → fix autonomously (respawn on transient throttle ≤1/tick, clear lock, etc.). No owner ping.
• BLOCKED-SAM-GATED — needs a human decision/approval/2FA/credential/business-or-design call → collect for STEP 4. NEVER guess these.
• FAILED — gave up → decide retry (corrected brief) vs escalate vs archive.

Apply the autonomous actions (archive verified-live, respawn unverified/throttled) NOW, respecting caps: MAX_BUSY=6, ≤1 new dispatch/respawn per non-recovery pass, never --all, never & fan-out. Record actions in ~/.claude/state/orchestrator-queue.jsonl.

STEP 3 — Render the dashboard for the owner

Show the --once table, then a 3-line summary: N agents · mac X / fra Y · working W · archived-this-pass A · respawned R · needs-you D. Keep it scannable. No walls of text.

STEP 4 — Surface ONLY the decisions (A/B/C/D)

For each BLOCKED-SAM-GATED item, present via AskUserQuestion as a real choice:

• A short header (the agent + what's blocked).
• 2–4 concrete options labelled, FIRST option = your recommendation (mark "(Recommended)").
• Each option's description = what happens if chosen.
• Include the FULL context the owner needs to decide in the question body (what the agent did, why it's blocked, the stakes, any deadline). the owner should never have to go digging.

Batch all decisions into ONE AskUserQuestion round (up to 4 questions). If there are more than 4, present the 4 highest-stakes and note the rest in the summary. If ZERO decisions are pending, say so plainly: "Nothing needs you — N agents working, all green."

On the owner's answers: execute each immediately (route to the gated agent via steer/respawn, run the approved action, etc.), then confirm one line each.

Modes

• /boss (default) — full pass: snapshot → triage → autonomous actions → dashboard → decisions.
• /boss --decisions — skip the table; jump straight to the A/B/C/D decisions (fast check-in).
• /boss --full — include spares + per-agent detail (deep look).
• /boss --archive-sweep — only the archive/respawn triage (cleanup pass, no the owner ping unless gated).

Cross-cutting rules

• VERIFY before relay (gh/curl/file). Never tell the owner "X is live" without the external check.
• ARCHIVE = finished + out of fleet (verified live). STOP/respawn = still in play. Never archive unverified work (owner directive).
• Outbound to anyone but the owner → staged, never auto-sent. Status to the owner → pre-authorized.
• Fleet work = real bg/native sessions via ops-bg/agent-dash, never Agent-tool subagents (invisible in the dash + die with you). Agent-tool only for in-context research/verification.
• FRA-host actions go over the agent-dash remote layer (control.mjs SSH), never a second orchestrator.