RCC is the ops layer above your AI coding agents. Claude Code and Hermes sessions across all your machines on one live board — watch them work, take any of them over, approve tool calls from your phone, and let scheduled runs keep working while you sleep.
Every session on every machine, sorted into live lanes: working, waiting on you, idle. Board, project, grid and map views — plus a PWA on your phone.
A session someone started in a terminal this morning? Take remote control of it from the browser or Telegram and keep the conversation going.
Tool calls wait for your allow or deny — in the console, or as Telegram buttons in your pocket. Hit “always” once and that command stops asking.
Cron-spawned sessions on each machine's own clock: nightly test triage, morning summaries — they run whether the console is open or not.
A session that goes quiet mid-run pings your phone. Each morning: one message with what ran overnight and what's blocked on you.
Question your entire transcript history — “which session fixed the nginx config, and how?” — answered with citations to the exact sessions.
RCC runs my own fleet every day; that's the demo above and the video. It isn't packaged for self-serve yet, on purpose: the first few people who need this get private trial builds, onboarded personally, in exchange for honest feedback about what you'd run it on.
One line about your setup is enough — how many machines, which agents.
tell me what you'd run it on →