A TUI-first agent control plane
Hangar lives inside ainb: a background daemon + a terminal-UI plugin talking over a token-gated unix-socket JSON-RPC link, backed by SQLite. Issues, a Kanban board, an agent fleet, skills, cron autopilots, a usage dashboard and a command palette — all driven from the keyboard. Press g from the ainb home to open it.
The grand tour — g to open, then tabbing through every screen: Issues · Task · Skills 3 · Autopilots 4 · Kanban K · Usage U · Inbox I · Logs L · Daemon D · Settings ,. Every frame is a real capture of the running TUI.
Issues, bucketed and assigned
Every workspace gets an issue board — Todo / In Progress / Done — with priorities and assignees. Here four issues sit in Todo, one routed to agent:Scout. Press 1 to land here from anywhere.
Create one without leaving the keyboard
Press c, type a title, hit Enter — the new issue lands in Todo. No mouse, no modal-juggling. Keystroke → RPC → row → re-render.
A task that actually ran
The Kanban task board tracks the real lifecycle — queued → running → done → failed. That #KPQN3V · 11m · done in the Done column is a task the daemon claimed, ran end-to-end, and finalized.
Cron autopilots dispatch the work
daily-triage fires on 0 9 * * *; its LAST RUN reads completed. Press r to fire one now — the scheduler enqueues a task, the daemon's claim loop runs it queued→running→done.
152 skills, scoped per workspace
Skills are imported per workspace and attach to agents. Agents themselves are minted from curated templates (code-reviewer, bug-fixer, …) with their bundled skills — and the same SKILL.md is re-materialised byte-identical into the agent's working dir at dispatch.
Ctrl+P — fuzzy search across everything
One palette searches issues, agents, skills and autopilots at once. Type dark, the matching issue surfaces ranked, Enter jumps straight to it. No more hunting tab by tab.
Live daemon health
Runtime, connection, claim-cache fill, in-flight concurrency and a 60-second throughput sparkline — all live. The grand tour above also walks the Usage token/cost rollup U, Logs L, Inbox I and Settings ,.
No daemon? A guided empty-state, not a void
When the daemon isn't running, the screen doesn't sit blank — it tells you what's wrong and how to fix it: a one-key s start, or the exact CLI to run. Empty states should teach, not stonewall.
Built & verified, not vibed
- Built to feature-parity with multica across the
agents-in-a-box-e38epic — every parity bead closed as an atomic, test-first commit. - CI runs the full 34-tripwire end-to-end suite on Linux and a launch-smoke subset on the weaker macOS runner — both green.
- A close-out verify-hangar walk (F01–F44 + R01–R08) passed 27 / 0 against real binaries + real SQLite — CLI, daemon and DB-resilience legs driven exactly as a sceptical user would.
- Hardening that shipped: a token-gated control-plane socket, a concurrency cap that holds at the boundary (no double-claim, no WAL deadlock), a poisoned-terminal retry taxonomy (a wedged conversation starts fresh instead of resuming), and a soak/backpressure test — 500+ events, zero drop/reorder, bounded RSS.