@remotehost/cli 1.0.1 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +80 -8
- package/THIRD-PARTY-NOTICES.md +0 -658
- package/bin/remote.js +158 -0
- package/dist/node-commands.js +66 -0
- package/package.json +15 -12
- package/dist/index.js +0 -67467
package/README.md
CHANGED
|
@@ -4,10 +4,17 @@ Create sandboxes, attach to them, and manage a fleet without leaving the
|
|
|
4
4
|
terminal.
|
|
5
5
|
|
|
6
6
|
```sh
|
|
7
|
-
|
|
7
|
+
curl -fsSL https://remotehost.ai/install | sh
|
|
8
8
|
remote login
|
|
9
9
|
```
|
|
10
10
|
|
|
11
|
+
That is macOS and Linux, where the script downloads the `remote` program and
|
|
12
|
+
needs nothing installed first. With npm, on any platform:
|
|
13
|
+
|
|
14
|
+
```sh
|
|
15
|
+
npm i -g @remotehost/cli
|
|
16
|
+
```
|
|
17
|
+
|
|
11
18
|
The command is `remote`.
|
|
12
19
|
|
|
13
20
|
## Getting started
|
|
@@ -81,9 +88,69 @@ expiring read/send token. Add `--approve` to allow tool-approval answers or
|
|
|
81
88
|
`remote mcp tokens` lists your tokens; `remote mcp revoke <id>` revokes one.
|
|
82
89
|
Personal tokens require the updated API and agent-token database migration.
|
|
83
90
|
They do not grant shell/file access or sandbox deletion. See
|
|
84
|
-
[agent sessions](../../docs/agent-sessions.md) for rollout status and native
|
|
91
|
+
[agent sessions](../../docs/workspaces/agent-sessions.md) for rollout status and native
|
|
85
92
|
terminal limitations.
|
|
86
93
|
|
|
94
|
+
## Connections
|
|
95
|
+
|
|
96
|
+
Connect Claude and GitHub once, for yourself; every sandbox you start is then
|
|
97
|
+
signed in as you, and never holds the tokens:
|
|
98
|
+
|
|
99
|
+
```sh
|
|
100
|
+
claude setup-token | remote connect claude # or: pbpaste | remote connect claude
|
|
101
|
+
remote connect github # enter the code it shows at GitHub
|
|
102
|
+
gh auth token | remote connect github --token-stdin # or a token you already have
|
|
103
|
+
remote connections # what is connected (--json)
|
|
104
|
+
remote disconnect claude
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
A token is read from stdin only, never from an argument or the environment;
|
|
108
|
+
on a terminal it is asked for and not shown. The Settings page "Connections"
|
|
109
|
+
in the console does the same. `remote broker sandbox-key <host> <name>` is
|
|
110
|
+
for the sandbox tooling: it prints a sandbox's key on stdout and refuses to
|
|
111
|
+
when stdout is a terminal (`--revoke` revokes it).
|
|
112
|
+
|
|
113
|
+
## Signing keys
|
|
114
|
+
|
|
115
|
+
An org's (or workspace's) Ed25519 key, held in Cloud KMS: its private half
|
|
116
|
+
never leaves it, and every signature is in the org's audit log.
|
|
117
|
+
|
|
118
|
+
```sh
|
|
119
|
+
remote signing-key create release # you are granted use of it
|
|
120
|
+
remote signing-key grant release service_account <id> # a CI identity's API keys sign with it
|
|
121
|
+
remote signing-key grant release sandbox <user-id> --sandbox cloudflare/dev
|
|
122
|
+
remote signing-key list # keys, public keys, grants (--json)
|
|
123
|
+
git cat-file commit HEAD | remote signing-key sign release --namespace git > commit.sig
|
|
124
|
+
remote signing-key revoke release <grant-id>
|
|
125
|
+
remote signing-key delete release
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
`sign` reads the message from stdin and prints only the signature: an SSH
|
|
129
|
+
signature (`ssh-keygen -Y sign`'s format, which `ssh-keygen -Y verify`
|
|
130
|
+
checks against the key's `ssh-ed25519` public key) by default, or raw
|
|
131
|
+
Ed25519 in base64 with `--format ed25519`. Inside a sandbox,
|
|
132
|
+
`--from-sandbox` signs as the sandbox with no sign-in: the fleet's egress
|
|
133
|
+
puts the sandbox's own identity on the request.
|
|
134
|
+
|
|
135
|
+
## mTLS services
|
|
136
|
+
|
|
137
|
+
A service your workspace's machines reach with mutual TLS, though no
|
|
138
|
+
machine holds a client key: a machine dials `<name>.svc.internal:<port>` in
|
|
139
|
+
plain TCP, and the fleet re-originates the connection as mutual TLS with a
|
|
140
|
+
short-lived client certificate for the machine's owner, from the service's
|
|
141
|
+
own client CA in Cloud KMS.
|
|
142
|
+
|
|
143
|
+
```sh
|
|
144
|
+
remote mtls-service create rbe --host rbe.example.com --port 8980 \
|
|
145
|
+
--server-ca buildbarn-ca.pem --client-dns-name untrusted.rbe.internal
|
|
146
|
+
remote mtls-service list # (--json)
|
|
147
|
+
remote mtls-service ca rbe > client-ca.pem # give this to the service to trust
|
|
148
|
+
remote mtls-service delete rbe
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
The workspace is the org's default Internal one unless `--workspace` names
|
|
152
|
+
another.
|
|
153
|
+
|
|
87
154
|
## Configuration
|
|
88
155
|
|
|
89
156
|
| variable | what it does |
|
|
@@ -94,8 +161,9 @@ terminal limitations.
|
|
|
94
161
|
|
|
95
162
|
## Requirements
|
|
96
163
|
|
|
97
|
-
Node.js 22 or newer. No other runtime dependencies — the
|
|
98
|
-
bundled file.
|
|
164
|
+
Installed with npm: Node.js 22 or newer. No other runtime dependencies — the
|
|
165
|
+
package is a single bundled file. The install script's `remote` for macOS and
|
|
166
|
+
Linux needs neither.
|
|
99
167
|
|
|
100
168
|
Because it is bundled, the open-source packages it depends on are compiled into
|
|
101
169
|
that file rather than installed beside it. Their licences and copyright notices
|
|
@@ -109,10 +177,14 @@ package.
|
|
|
109
177
|
|
|
110
178
|
## Local development
|
|
111
179
|
|
|
112
|
-
`remote-staging` runs `
|
|
113
|
-
checkout
|
|
114
|
-
|
|
115
|
-
|
|
180
|
+
`remote-staging` runs the Rust CLI, `clients/remote`, from the local root
|
|
181
|
+
checkout against `https://api-staging.remotehost.ai` (REM-6873):
|
|
182
|
+
`clients/remote/scripts/remote-staging` builds it when a source changed and
|
|
183
|
+
runs it under that name, so an edit there takes effect on the next launch.
|
|
184
|
+
It no longer runs this package, and an edit to `packages/cli/src` does not
|
|
185
|
+
change it. `src/index-staging.ts` is this package's own staging entry, which
|
|
186
|
+
its tests and the bundle (`index-staging.js`) still use. Staging keeps its
|
|
187
|
+
own login session.
|
|
116
188
|
|
|
117
189
|
`remote` is the npm registry installation of `@remotehost/cli`; keep it separate
|
|
118
190
|
from local builds and workspace links.
|