Omarchy Crew Chief Entry

Crew Chief

Every running AI coding agent session in your Omarchy bar, any harness, and a loud pill the moment one is blocked waiting on you.

You're running four agent sessions across four projects. Maybe Claude Code in two, Codex in one, Goose in another. One of them has been sitting on a permission prompt for six minutes. Which one? Crew Chief knows. A bar pill counts your running sessions, `󰋎 4`, and the moment a session is blocked waiting on you or finishes its run, the pill goes loud in your theme's active color: `󰋎 2 need you`. The panel lists the whole fleet, attention first: project, harness, state, how long it's been waiting, and the actual prompt it's stuck on.


The existing agent widgets tell you about your *quota*. Crew Chief tells you **who needs you right now**, fed by each harness's own lifecycle events, not by polling a usage API.

[](https://ko-fi.com/U5S225PTME)

Works with every make and model

Crew Chief is harness-agnostic by design: the widget watches a spool of tiny JSON state files ([the protocol](docs/PROTOCOL.md)), and anything that can run a command can report in. Three integration tiers:

Harness	Integration	States you get
Anything running under Herdr, whose detection roster covers Claude Code, Codex, Amp, Cline, Copilot, and more	zero config: when herdr is installed, the widget snapshots herdr agent list on every poll (herdrSync setting, default On, harmless no-op without it)	working / needs you (blocked) / done, with the pane title as context
Claude Code (standalone)	first-class hook adapter, one-command install (below)	working / needs you / done, with the blocking prompt
OpenAI Codex (standalone)	adapters/codex-notify wired into notify in ~/.codex/config.toml	done