OPEN-SOURCE REMOTE CODING

Your existing dev server.
A workspace you can take with you.

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

ONE TASK. SAME WORKSPACE.HOST → BROWSER
ccr-cloud / dev-box Connected
~/src/my-app · task worktree
Improve the search flowNeeds approval
YOUAdd keyboard navigation and test the empty state.
CLAUDEI’ve prepared the change. Please review the test command before I continue.
$ npm test -- --runInBand
Waiting for your approvalDeny Allow once
Your next instruction…Send ↗

Interactive illustration, not a live session.

01 Your infrastructure02 Existing credentials03 Separate task worktrees04 MIT licensed
BUILT AROUND YOUR SERVER

Keep SSH and tmux.
Add a task workspace.

SSH gets you onto the machine. tmux keeps processes running. ccr-cloud adds a browser workflow around your Claude Code tasks.

Separate task worktrees

Give each task its own branch and checkout. Keep your original checkout and uncommitted changes where they are.

Host tasks run with your server account’s permissions. A worktree separates files; it is not a security sandbox. Read the security model ↗

Remote control for
the setup you already trust.

You already have a development machine that works. Bring that environment with you—without moving your repositories into another hosted workspace.

Runs as your server user

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.

Your browser or PWA YOU DECIDE
↓ authenticated connection ↑
Your host control plane SESSION HISTORY
↓ acknowledged runner link ↑
Claude Code HOST
Task worktree GIT

What you can do today.

Everything here ships in the current release. Proposed features live on the roadmap, clearly labeled.

01 /

Approve where you type

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 ↗
02 /

Answer from the notification

Allow once or Deny straight from a push notification. Allow is offered only for read-only tools inside the task's workspace.

Read how ↗
03 /

Review changes, then open a PR

See what each turn changed as a diff, then create a pull request from the task when you're happy with it.

Read how ↗
04 /

Prepare every task the same way

Give a repository a setup script and variables. Each new task runs it once, before Claude starts.

Read how ↗
05 /

Pair a phone without typing a token

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 ↗
06 /

Switch models at a usage limit

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).

First task.
Then your real work.

Start with a scratch task over your existing SSH connection. Choose phone access after the first reply works.

ON YOUR SERVER
git clone https://github.com/thinkinginmath/ccr-cloud.git
cd ccr-cloud
npm ci
npm run setup -- --start
Existing model and Git credentials stay on your host.
BEFORE YOU BEGIN

A small set of prerequisites.

Node 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 ↗
Host mode uses your server account’s access. A worktree is workspace separation, not a security sandbox.

Understand the workflow.
Own the details.

Practical notes from building a phone-friendly interface around a real development environment.

Build on the open-source core.

Start with Claude Code on your own server. Follow development, report issues, or contribute a bounded improvement. Proposed capabilities are tracked separately.