AkaraChen/cc-remote
Claude Code with the model on a remote host and the tools on your machine
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
Claude Code as an ACP agent. The model runs on a remote host, and the tools run on your machine. You keep claude installed and logged in on one server. cc-remote reaches it over plain ssh and runs every file read, edit and shell command locally, in the session's directory. Any ACP client can use it: Zed, paseo, and others. The server only needs claude. Nothing else gets installed there, and your machine doesn't need claude at all. cc-remote is claude-agent-acp with one change: the claude it starts runs on the server. Sessions, permission prompts, modes, models, forks and diffs all work the way they do in claude-agent-acp. Before you start, have these two in place: put ports, users and jump hosts in /.ssh/config). Run claude there once and log in, or use cc-remote --cli auth login after installing. On your machine you need Bun to build cc-remote. The binary…
Read the full README ↗ · Preview checked 2026-11-08T12:30:21.213Z
Inside the original README — Document outline
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
What this repository does
Claude Code with the model on a remote host and the tools on your machine
Repository facts
- Owner
- AkaraChen
- Primary language
- TypeScript
- Stars
- 322
- Forks
- 38
- Open issues + pull requests
- 0
- License
- Not reported — inspect the license file
- Archived
- No
- Default branch
- main
- Created
- 2026-11-01T09:49:24.000Z
- Last push
- 2026-11-04T01:12:04.000Z
Topics and intended use
No topics were included in the latest source metadata.
Review the README for scope, installation, examples and limitations. We do not run repository code or certify it.
Evaluate before installing
Review licensing and dependencies, inspect recent commits and unresolved issues, and test in an isolated environment before production use. Stars and forks alone cannot answer these questions.
Source and freshness
Source: GitHub. Metadata observed 2026-11-08T12:21:27.846Z. Daily imports are snapshots, not real-time monitoring.
Popularity and source listings do not establish security, suitability, licensing rights or benchmark performance.