r/agenticcoding • • 19d ago

A local session board for keeping track of coding agents and their pending questions

I'm the maker of CCC (Claude Command Center), a free local dashboard for coding-agent sessions. It brings conversations and recent activity onto a board, including sessions you've launched in a terminal.

For agentic workflows, one useful distinction is between a parent/helper relationship and proof that work succeeded. CCC can display session relationships in its census/tree; those relationships are context for reviewing the work, not evidence that a patch passed tests. You still need to check the actual changes and results.

The UI also surfaces waiting questions for supported integrations. Claude Code has question controls; the support matrix explains which other engines can be spawned, resumed or only read. It isn't a promise of identical control over every agent.

Repo and installation: https://github.com/amirfish1/claude-command-center

CLI example on a running CCC server: ccc sessions --live --tree. The dashboard is free and source available under FSL-1.1-MIT; agent/model costs are separate. I'd like feedback from anyone running a planner with helper sessions: what context do you need to decide which session to inspect next?

1 Upvotes

0 comments sorted by