ainb-fleetstandup

Solid

Show fleet status — every claude session running on the host, merged across ainb + claude-peers broker + background jobs. Use when you need to enumerate sessions before composing an action, check the `summary` of each session, or pipe the list into jq for filtering. (Writes go via tmux by default; a `peer_id` is just an extra discovery signal / fallback channel, not a routing requirement.) Default output: text table. Pass --format json for LLM consumption.

AI & Automation 18 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# ainb fleet:standup List every claude session across the host. Three sources merged + deduped by cwd. ## What standup reads vs what `needs` reads `standup` is a **roster**: it merges discovery sources (ainb + claude-peers broker + background jobs) and attaches a JSONL-synthesised `summary` line per session. It does **not** read the event-sourced `current_state` table itself — it is a "who is running" snapshot, not a "who is blocked" classifier. The block-detection lives in [`/ainb-fleet:needs`](../needs/SKILL.md), which is **hooks-primary**: it reads the materialized `current_state` table (ASK / ERR / WAIT / IDLE / RUNNING / DONE), sourced from Claude Code hooks via `events.jsonl` → notifyd, with a tmux/transcript fallback for non-Claude agents (Codex/Gemini fire no Claude hooks). Standup's job is to spot when a session *looks* answerable (`summary` contains `AskUserQuestion`) and **auto-chain to `needs`** for the authoritative read + routing (see below). > Neither skill installs hooks — they consume materialized state. The global > Claude Code hooks are installed by [`ainb fleet atc setup`](../atc/SKILL.md). ## Run ```bash ainb fleet standup # text table (default) ainb --format json fleet standup # JSON for piping ainb fleet standup --no-enrich # 0-token roster (env AINB_FLEET_ENRICH=0) ``` `--format` is a **global** flag — it may appear anywhere (`ainb --format json fleet standup` or `ainb fleet --format json standup` both wo...

Details

Author
stevengonsalvez
Repository
stevengonsalvez/agents-in-a-box
Created
1 years ago
Last Updated
today
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ainb-fleet

Fleet orchestration overview — the `ainb fleet ...` Rust subcommand namespace for driving every claude session on the host. Routes to the sub-skills (standup / broadcast / sequence / needs / daemon / atc). Invoke this for an at-a-glance map of what fleet can do; reach for the specific sub-skill for the verb you want.

18 Updated today
stevengonsalvez
AI & Automation Solid

ainb-fleetdaemons

Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a pid-recycle. Use this when you need to answer "are my background daemons actually alive?" — not just installed, but serving. Default output: a fixed-width text table. Pass --format json for tooling.

18 Updated today
stevengonsalvez
AI & Automation Solid

ainb-fleetneeds

Center control panel — enumerate every claude session that is blocked waiting on something: a user answer (AskUserQuestion fired), an API error retry, an idle assistant turn-end with no follow-up, or an explicit WAITING: marker. Returns rich JSON with signal kind + context per session. Use this when you've stepped away from the fleet and want one place to see everything that wants your attention and answer it.

18 Updated today
stevengonsalvez