Legbar – live AI agent sessions beside GitHub CI, in one terminal

Legbar, a new open-source terminal tool from developer gmhoward9289-ops, displays live AI agent sessions and GitHub CI status side-by-side in one screen, merging data from the roost and leghorn discovery layers to prevent discrepancies. The tool, installable via pipx, pip, npm, brew, winget, or apt, supports Python 3.9+ and works on macOS, Linux, and Windows, with features like --json output and LEGBAR_* environment variables for configuration.

One screen for the whole fleet: live agent sessions beside GitHub CI , drawn from a single discovery layer so the two panes can never disagree. roost answers what are the models doing . leghorn answers what are the repos doing . Both are true at once and neither view contains the other — so watching a fleet has meant watching two windows and joining them by eye. legbar draws both lanes on one canvas. legbar 5 sessions | 1 cursor | 1 need input | 15 ci red | 125k held | 18:37:00 SESSIONS CI / PRS -------- -------- cc heron-ops-3c FB5 ------- 32% needsinput dev X roost ci cc swamp-ops-ad OP5 ------- 25% working dev X roost 56 ci: skip winget~ cc heron-ops-16 FB5 --------- 10% working dev X copilot-money~ Tests cc claude-10 OP5 --------- 8% idle Claude leghorn release cu c5468eb1 - - idle dev . leghorn 61 checks pending The short ambient loop below is the same program, idling — which is how it spends almost all of its time: Both are real legbar, unmodified, reading a staged fleet — see demo/ /gmhoward9289-ops/legbar/blob/main/demo for how it is built and how to re-record. The second contested row is the one worth looking at: a Claude session and a Cursor agent in the same working copy. Cursor writes no session marker and no claim, so a dashboard reading only Claude's session directory cannot see that collision at all. SESSIONS — every live agent on the machine. Claude Code sessions are joined by pid against ~/.claude/sessions/<pid .json , with model, context burn, and status read from the session's own JSONL transcript. Cursor agents appear too , marked cu — Cursor writes no session marker and no claim, so a fleet view that only reads Claude's session directory is blind to every Cursor agent running beside it. CI / PRS — GitHub Actions runs and open pull requests across every clone, with failures pinned so a red build cannot scroll away. pipx install legbar Python 3.9+, standard library only. Works on macOS, Linux and Windows. legbar also publishes to a few other channels, picked automatically off the same release: pip install legbar if you'd rather skip pipx npm install -g legbar Node's on the box already anyway brew install gmhoward9289-ops/tap/legbar macOS / Linux winget install gmhoward9289-ops.legbar Windows Debian and Ubuntu can add the signed apt repo instead of a one-shot .deb : curl -fsSL https://gmhoward9289-ops.github.io/legbar/legbar-archive-keyring.asc \ | sudo gpg --dearmor -o /usr/share/keyrings/legbar-archive-keyring.gpg echo "deb signed-by=/usr/share/keyrings/legbar-archive-keyring.gpg \ https://gmhoward9289-ops.github.io/legbar stable main" \ | sudo tee /etc/apt/sources.list.d/legbar.list sudo apt update && sudo apt install legbar Windows without a package manager: grab the frozen .exe zip from the latest release https://github.com/gmhoward9289-ops/legbar/releases/latest . legbar the full-screen view legbar --once render one frame and exit pipes, CI, screenshots legbar --json the joined state, for piping somewhere else legbar --no-git skip git probing if it is ever slow legbar --no-ci skip the gh sweep offline, or when it is slow In the full-screen view: q quit, g toggle git probing, r refresh now. Every override is LEGBAR . The older roost / leghorn / ccwork variable names are still honoured, so an existing install keeps whatever it had configured; the new name wins when both are set. | Variable | Default | What it points at | |---|---|---| LEGBAR REPOS ROOT | ~/GitHub | where the clones live | LEGBAR SESSIONS DIR | ~/.claude/sessions | live-session markers | LEGBAR PROJECTS DIR | ~/.claude/projects | session transcripts | LEGBAR CURSOR HOME | ~/.cursor | Cursor's agent transcripts | LEGBAR CURSOR MAX IDLE SECS | 86400 | how far back a Cursor agent counts as live | LEGBAR BACKENDS | claude,cursor | which discovery lanes run at all | Cursor liveness is inferred, not probed. A Claude row means this process exists os.kill pid, 0 . A Cursor row means this transcript moved recently — Cursor writes no pid to join against. That is a weaker signal and it is labelled as one; pid is None for Cursor rows rather than invented. Cursor's project slugs are lossy. The slug joins path parts with - , and - is legal inside a directory name, so c-Users-me-dev-heron-ops reads equally as dev/heron/ops and dev/heron-ops . legbar resolves each segment longest-first against what actually exists on disk. A slug that resolves nowhere — another machine's checkout, a deleted clone — falls back to the naive split rather than raising. Block-drawing characters mojibake in the Windows console, so the context bars, the pane rules and the status glyphs are all plain ASCII. Same constraint roost 's sparklines and leghorn 's tables are built around. , o \ / \ | ====== | | ====== | \ ==== / \ / || || ^^ ^^ legbar reads transcripts and registries, and runs git and gh in read-only modes. It never writes to a repo. — roost https://github.com/gmhoward9289-ops/roost top for Claude Code: per-session context burn, models, and the subagents a session spawned.— the repo lane on its own: sessions joined to worktrees and real git state, CI, and a commit feed. leghorn https://github.com/gmhoward9289-ops/leghorn legbar — both lanes on one screen, over one discovery layer. henhouse.py is that discovery layer: sessions, transcripts, git, GitHub, and Cursor. It is a working CLI in its own right python henhouse.py . MIT