ainb-fleetbridgelisted
Install: claude install-skill stevengonsalvez/agents-in-a-box
# ainb fleet:bridge — native phone bridge
A single-binary, two-way relay between a chat channel and your ainb fleet.
It folds every channel into the ainb binary — there is no separate Python
runtime to install or manage. Three channels share ONE relay/routing core over
one transport:
- **Telegram** — long-polling `getUpdates` over HTTP.
- **Slack** — socket-mode WebSocket.
- **Discord** — raw Gateway WebSocket.
```
chat message ──▶ bridge ──parse target──▶ tmux send-keys ──▶ ainb session
reply ◀── bridge ◀──capture from JSONL transcript tail ◀──┘
```
This is ATC's voice to you: when ATC escalates, the `NEED: …` line surfaces in
whichever channel the bridge runs.
## Subcommands
```bash
ainb fleet bridge run # start the daemon (default if no subcommand)
ainb fleet bridge install # install as a launchd/systemd service (idempotent)
ainb fleet bridge uninstall # remove the service unit (returns the removed path, if any)
ainb fleet bridge status # report INSTALL state of the service unit
```
`run` loads the config and drives every configured channel concurrently; it
runs until the process is stopped. `bridge` with no subcommand is the same as
`bridge run`.
> **`status` reports INSTALL state, not liveness.** For "is the bridge actually
> running and connected right now?" use [`/ainb-fleet:daemons`](../daemons/SKILL.md)
> — its heartbeat-backed probe distinguishes a live+connected bridge from a
> crashed one (stale heartbeat / recycled pid