agent-buslisted

# agent-bus Turn your Claude / Codex / Cursor / Gemini sessions on the same machine into a local agent team. Each session registers a name, then you can send messages, ask blocking questions, delegate tasks, broadcast to channels, message scoped teams, route work by capability/role, track agent status, record decisions and memories, record task progress, generate session briefs, and produce merge-readiness reports — all through one SQLite file at `~/.agent-bus/bus.db`. This skill is the **coordinator playbook**: when the user speaks naturally, you translate their intent into agent-bus tool calls. ## Setup check (do this first) Before using any bus tools, run `scripts/check-setup.sh`. If it exits non-zero, halt and show the user the install hint it printed. Do not try to use the bus until the check passes. If the user asks you to fix the setup, run `scripts/check-setup.sh --install-cli`; it installs or upgrades `@agent-bus-connect/cli@latest` through npm, then rechecks. If `mcp__agent-bus__register` is not in your available tools, the MCP server is not wired into this session. Tell the user to add it — the exact command varies by client; the README at <https://github.com/MustaphaSteph/agent-bus#install> has each. ## Identity This session is the **coordinator**. At the start of any bus interaction: 1. Call `register` with a stable name and a concrete `team`. Ask the user once for any missing name or team, then reuse both for the rest of the session. Default the na