Stith
In DevelopmentThe control plane for every coding agent on your machine
A always-on operator console for AI coding agents. It ingests the full lifecycle-hook stream from every session across every config root and both host environments, so it can say what each agent is doing, which account it is spending, and which repository it holds — then act on that: switch accounts before a quota runs out, queue two sessions off the same repo instead of letting them collide, and reach a session from a browser, a terminal, or a Stream Deck key.
Screenshots are on their way — Stith doesn't have a capturable public surface yet.
Key Features
- Live fleet view fed by 29 real lifecycle hook events, not screen-scraping
- Multi-harness — a curated registry of coding agents, detected by binary rather than assumed
- Account and quota management with auto-switching before a session hits its limit
- Per-repository claim queue that stops two agents writing the same tree
- Two surfaces over one daemon — web app and Rust TUI — plus a Stream Deck plugin shipped separately as aylith-labs/stith-deck
- Full-text search across every transcript in every config root
Built For
Anyone running many coding-agent sessions at once across several accounts and machines, who has lost track of which one needs them
Why
One agent is easy to watch. A dozen, spread across config roots, accounts and two host environments,
is not — and the failure is quiet: a session sits waiting on a question nobody sees, an account burns
its weekly quota on a background job, two agents rewrite the same file.
Stith is the layer above them. It never runs the agent and never becomes the terminal it lives in;
it watches, governs and coordinates whatever is already running, including the sessions it did not
start. That is deliberate — a control plane that only governed what it launched would cover strictly
less than one that reads the hooks every session emits anyway.