Separate task worktrees
Give each task its own branch and checkout. Keep your original checkout and uncommitted changes where they are.
Use the Claude Code and Git setup already on your server. Give each task its own worktree, review commands and changes, and send follow-ups from your browser or phone.
Self-hosted · MIT licensed · Your existing Claude Code setup
Interactive illustration, not a live session.
SSH gets you onto the machine. tmux keeps processes running. ccr-cloud adds a browser workflow around your Claude Code tasks.
Give each task its own branch and checkout. Keep your original checkout and uncommitted changes where they are.
Reopen the task to read its recorded activity and send the next instruction. See recovery guarantees ↗
Host tasks run with your server account’s permissions. A worktree separates files; it is not a security sandbox. Read the security model ↗
You already have a development machine that works. Bring that environment with you—without moving your repositories into another hosted workspace.
The control plane and agent run on your infrastructure, using the Claude and Git access you configure there. No account with us, routing gateway or hosted coding plan is required for host mode.
Open the same task from a browser or installed PWA. Agent execution stays on the server.
Everything here ships in the current release. Proposed features live on the roadmap, clearly labeled.
Approval cards sit just above the message box with the full command or path. When several are waiting, Approve all lists each one before you confirm.
Read how ↗Allow once or Deny straight from a push notification. Allow is offered only for read-only tools inside the task's workspace.
Read how ↗See what each turn changed as a diff, then create a pull request from the task when you're happy with it.
Read how ↗Give a repository a setup script and variables. Each new task runs it once, before Claude starts.
Read how ↗Open a one-time link on the phone to sign it in. Revoke a lost device and it is signed out at once.
Read how ↗Resume a task through your CCR gateway on another model, such as an open-source one, and switch back later.
Read how ↗Prefer chat? Control tasks from an owner-only Discord bot, or try experimental WeChat and WhatsApp pairing (off by default).
Start with a scratch task over your existing SSH connection. Choose phone access after the first reply works.
git clone https://github.com/thinkinginmath/ccr-cloud.git
cd ccr-cloud
npm ci
npm run setup -- --startNode 22.18+, Git, tmux, and a working Claude Code installation on your server. Host mode needs neither Docker nor CCR.
Setup prints your laptop connection command and how to retrieve your owner token. Then try New → Scratch task → Reply OK.
Follow the complete getting-started guide ↗Practical notes from building a phone-friendly interface around a real development environment.
Installation, local repositories, GitHub access, phone networking, and the checks that matter.
Read the guide ↗Persistent servers, existing credentials, and a remote control that leaves execution in your hands.
Read the article ↗Separate model, repository, and networking checks instead of debugging all three at once.
Read the article ↗Start with Claude Code on your own server. Follow development, report issues, or contribute a bounded improvement. Proposed capabilities are tracked separately.