Why I built it: a coding agent ships a feature in an afternoon, and three people and five sessions later nobody can answer "what is in flight, what did it cost, why was it decided this way". The answer I landed on is not a dashboard but a method where every decision and every delivery is a versioned file: a handful of docs written once, a queue with one line per delivery (docs/06), and one page per delivery (work/<slug>.md) that says what will be built and how it is proven before any code changes. The method is four slash commands the agent reads from one file (brainstorm, analyze, propose, apply); it works without FACE. FACE is the window: the queue becomes a five-lane board, a card opens into the page plus the live session, and the commit window shows exactly what the agent staged. The agent never commits or merges; you click.
I built FACE itself with it, from the fourth week on. Before that the same method shipped a job marketplace in 89 one-page deliveries over 14 days, and a consulting project in 107 deliveries over 19 days.
Install: `brew install jckodel/face/face`, `winget install JCKodel.FACE`, a `.deb`, or `curl -fsSL https://face.kodel.com.br/install.sh | sh`. macOS, Linux, Windows, arm64 and amd64. UI in en, pt, es, fr, de and zh-Hans.
What is missing: single user and local only (a team mode with a server on your network is the next milestone); no editor (it shows code and diffs, your editor stays your editor); the source is not public yet. It will be visible under a fair source license when the paid tier for teams exists, and the free tier stays free. By itself FACE makes at most two requests, both off until you turn them on: a daily anonymous ping that counts machines and a daily version check. The page "What FACE sends" lists both URLs.
Happy to answer anything about ACP, the adapters for Claude and Codex (they are not ACP native, so FACE wraps them), or the method.