I’m the maker of CCC, a local dashboard for coding-agent sessions. One design issue in the attached demo is that a session can be marked working while it still has a question for the human. A progress indicator alone does not communicate the decision waiting on the operator. The practical approach shown is a shared session board plus the actual question card and actions in the conversation pane. Parent/helper grouping retains why a helper session exists. The question reply in the clip reaches a real Claude Code hook, with staged sessions rather than a benchmark. A second lesson is that a shared UI does not imply a shared execution API. Transcript formats and steering controls vary by engine, so adapter capabilities need explicit boundaries. The code and support matrix are linked below. https://github.com/amirfish1/claude-command-center Free local dashboard; model/provider fees are separate. Source available under FSL-1.1-MIT. Demo uses real UI, staged sessions and AI voiceover; the real question-hook interaction is Claude Code. 33-second video demo: https://www.reddit.com/r/ClaudeCode/comments/1xeot43/i_kept_missing_questions_from_my_coding_agents_so/ submitted by /u/amirfish
Originally posted by u/amirfish on r/ArtificialInteligence
You must log in or # to comment.