You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.en.md
+43-27Lines changed: 43 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Out-of-the-box isolated cloud hosts for Claude Code and dev teams. Pre-installed
24
24
## Features
25
25
26
26
-**One-command access** — `curl | bash` to authenticate, create container, and SSH in. Zero user config
27
-
-**cloud-claude local CLI** — `alias claude=cloud-claude` to transparently run remote Claude Code from your local terminal with real-time directory mapping
27
+
-**cloud-claude local CLI** — `alias claude=cloud-claude` to run remote Claude Code from your terminal; local cwd is sshfs-mounted at the **same path** in the container; optional local exec for commands like `git`
28
28
-**Claude Code ready** — Pre-installed in every container. All API requests auto-routed through designated exit IP
29
29
-**Full-tunnel egress** — sing-box tun + Linux netns full-tunnel, nftables default-deny, no DNS/WebRTC leaks
@@ -89,7 +89,7 @@ Log into the admin dashboard, then:
89
89
1.**Add egress IPs** — Multiple proxy protocols, with one-click connectivity test
90
90
2.**Create users** — Set username, password, expiration
91
91
3.**Create hosts** — Create container for user and bind egress IP
92
-
4.**Share access command** — Copy the `curl` command from host detail page
92
+
4.**Share access info** — Copy the `curl` command from host details; for `cloud-claude` users also share: **gateway HTTPS URL**, **host Short ID**, and **user password**
# Enter password → wait for boot → auto SSH into cloud host
101
101
```
102
102
103
-
### cloud-claude (Local CLI, Transparent Remote)
103
+
### cloud-claude (local CLI, recommended)
104
104
105
-
Besides SSH access, you can use the `cloud-claude` binary on your local machine to transparently run remote Claude Code with your current directory auto-mapped into the container.
105
+
After the admin **creates the host, binds an egress IP**, and the container is ready, give the user three things:
106
106
107
-
**Install:**
107
+
| Field | Meaning |
108
+
|-------|---------|
109
+
|**Gateway URL**| Public HTTPS base URL of the control plane, e.g. `https://gw.example.com` (same origin you use for the admin UI in the browser; usually **not** the `:3000` admin dev port) |
110
+
|**Short ID**|**Host** short ID from the host detail page. If the user configures a **user** short ID instead, they connect to that user’s primary host |
111
+
|**Password**| The user’s password from the admin dashboard |
112
+
113
+
Install the CLI once, run `init`, then from **any project directory** run `cloud-claude` — the cwd is mounted at the **same path** in the container. By default `git` runs locally (tune with `proxy_commands` in `~/.cloud-claude/config.yaml`).
`cloud-claude` automatically: authenticates → waits for container ready → maps your current directory to `/workspace` via sshfs → launches Claude Code remotely. Terminal resizing, signals, and exit codes are all properly forwarded.
171
+
**Optional:** set `proxy_commands` in `~/.cloud-claude/config.yaml` (list of command names to run on the host). Default is `git` only; use an empty list to disable.
172
+
173
+
`cloud-claude` does: gateway auth → wait for container → sshfs mount at the same path → start Claude Code remotely. Terminal size, signals, and exit codes are forwarded.
158
174
159
175
### Claude Code (via SSH)
160
176
@@ -178,7 +194,7 @@ Containers include KasmVNC + Chromium. Access the browser desktop via admin or u
178
194
┌───────────────────────────────────┐
179
195
User ──curl──> Control Plane (:8080) ──Docker──> │ User Container │
0 commit comments