agbridgelisted
Install: claude install-skill zahark/agbridge
# agbridge
Agents on remote Linux hosts write their state to a shared directory. The Mac **pulls** that state
over one long-lived `ssh` and renders it as rows in [agterm](https://github.com/umputun/agterm)'s
sidebar. No reverse tunnel, no sockets, no daemon on the cluster.
**Answer from this file where it is covered. For anything else, read the docs listed at the bottom
rather than guessing — this project's own rule is that a claim about agterm or the wire is verified,
never inferred.**
## The mental model
Three machines, one direction of flow:
```
cluster host: agb hook -> writes <statedir>/sessions/<host>/<key>.{json,state}
cluster host: agb feed -> reads them, streams NDJSON over the Mac's ssh
Mac: agb bridge -> owns key -> agterm row, calls agtermctl
Mac: agb pane -> what a row runs when you click it
```
That whole column is **one instance**, and on the Mac every instance is **named**: `install.sh mac`
requires `--instance <name>` and refuses an install without one. A machine that shares no disk with
the first gets another instance — its own statedir, feed and bridge, a second launchd job, rendering
into the same sidebar. So read every Mac path below as `~/.config/agbridge/<name>/…`, and see *Add a
machine that shares no disk* for the rest.
Two facts explain most confusion:
- **Liveness is proven, never inferred.** No age is ever turned into a status. A row is removed only
when death is proven (`kill(pid,0)` plus a `starttime` match), whi