I'm the maker of Claude Command Center (CCC). I built it because switching between coding-agent sessions made it too easy to miss a question or lose track of which session needed me. CCC puts the sessions on one local board, with summaries, conversation views, and parent/helper grouping. Claude Code and Codex are the main workflow shown here; other integrations have different levels of control. It runs on your own machine, with a Python standard-library server and a browser UI. The useful design lesson for me has been that “working” and “needs a human” are different questions. In this demo a session can still look green while it has a question waiting. The question card is what makes the next action clear. 33-second video: https://www.reddit.com/r/ClaudeCode/comments/1xeot43/i_kept_missing_questions_from_my_coding_agents_so/ The clip uses the real UI with staged demo sessions and an AI voiceover. The question-hook interaction is real; the Grok/Devin rows are demo data, not a live multi-provider benchmark. Project and install docs: https://github.com/amirfish1/claude-command-center CCC is free to use under FSL-1.1-MIT (source available); model/provider subscriptions are separate. For people juggling several sessions: does the board make the next action obvious, or would you want a simpler “needs me” inbox?   submitted by   /u/amirfish [link]   [comments]