Wizards Helm

One place to see what coding sessions are doing, what they need from me, and what the persistent bot fleet owes next.

Real work across monitors

Helm reads live session events from Claude Code, Codex, Cursor and supported Grok sources, and hosts its own coding terminals. Mission, chats and bridge views share the same event model. A compact control pill hides or restores the walls, and decisions can be reached without changing the order of the work under the pointer.

A fleet with obligations

Persistent bots have charters, goals, routines, inboxes and a chain of command. The fleet view brings open questions, permission requests, queued work and owed decisions together. Bots wake through the controller under their configured state and account limits. A bot turn uses the selected provider subscription or account.

Live and replay stay distinct

Recorded sessions can be replayed while current work stays visibly separate. Hosted terminals, headless runs and repository comparison views are different ways to inspect or direct real work. Hooks relay events; parsers turn provider-specific transcripts into one shared shape.

The useful constraint

The wall should tell me what changed and where I need to act. It reads existing sessions without taking them over, keeps local state local, and uses the coding providers for the sessions I explicitly run. The project is in active private use; this page does not offer a public installer.