Reboot-surviving Claude remote-control server sessions
A new tool called crc has been developed to manage Claude Code remote-control server sessions, addressing issues with disconnections and reboots. It runs a Claude Code remote-control server for each repository within its own tmux session, ensuring automatic restarts after reboots on macOS (launchd) and Linux (systemd). The tool also restarts sessions if they die and assigns each chat its own git worktree to prevent overwrites, allowing old sessions to be revived.
- Published
- 09/08, 02:07 UTC+0
- Ingested
- 09/08, 03:00 UTC+0
- Source type
- Dev community
- Tier
- Community
- Source status
- Healthy
Tier is a per-source editorial setting, not a per-item score.
My Claude Code remote-control sessions disconnected every time I closed my laptop lid. This was unpleasant. This forced me to move all my AI coding onto the Mac Mini at home and run it all in the "remote-control server" mode. That worked really well - until the Mini rebooted. Nothing came back, and I couldn't figure out how to get the old sessions going again.
So, Claude and I experimented with tmux and claude remote-control server session recovery options, and wrote a small tool to handl all of it: crc. It runs a Claude Code remote-control server per repo, each in its own tmux session, and starts them again after a reboot (launchd on macOS, systemd on Linux). If one dies, it restarts it. Each chat gets its own git worktree, so two chats in the same repo don't overwrite each other. Old sessions can be revived instead of lost.
brew install devsecopsinc/tap/crc https://github.com/devsecopsinc/claude-remote-control
It's bash, MIT, no dependencies beyond tmux and git. Pretty early and built around my own setup, so there are rough edges. If you run agents on a box at home or in the cloud, it might be useful. Let me know if it breaks.
Hope you find it useful. As to me, I absolutely enjoy using it.