@archme/cli 0.20.0 → 0.22.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/SKILL.md +36 -0
- package/dist/cli.js +908 -559
- package/package.json +1 -1
- package/sandbox-image.json +1 -1
package/SKILL.md
CHANGED
|
@@ -243,6 +243,42 @@ You are the agent of correctness:
|
|
|
243
243
|
- The server returns warnings (e.g., `unanchored:true` with non-empty
|
|
244
244
|
anchors); they don't block writes but indicate something to clean up.
|
|
245
245
|
|
|
246
|
+
### Daemon agent env
|
|
247
|
+
|
|
248
|
+
A daemon job that runs **unboxed** (sandbox off, a shadow-mode fallback, a
|
|
249
|
+
local-poll repo), plus the host-side board triage and digest, gives its
|
|
250
|
+
Claude Code only the **agent env**: `PATH`, `HOME`, `USER`, `LOGNAME`,
|
|
251
|
+
`SHELL`, `TMPDIR`, `TZ`, `LANG`, `TERM`, `LC_*`, the proxy variables
|
|
252
|
+
(`HTTPS_PROXY`/`HTTP_PROXY`/`NO_PROXY`, either case), `NODE_EXTRA_CA_CERTS`,
|
|
253
|
+
`CLAUDE_CONFIG_DIR`, `CLAUDE_CODE_OAUTH_TOKEN`, `ANTHROPIC_API_KEY` and
|
|
254
|
+
`ANTHROPIC_BASE_URL`. Every other variable in the daemon's env (`GH_TOKEN`,
|
|
255
|
+
`AWS_*`, …) stays out of the agent's reach. `archme scan`, `init` and
|
|
256
|
+
`doctor` run on your own machine for you, so their Claude gets your env
|
|
257
|
+
unchanged.
|
|
258
|
+
|
|
259
|
+
If your Claude authenticates another way (Bedrock, Vertex, an LLM gateway),
|
|
260
|
+
name the extra variables in `ARCHME_CHILD_ENV_PASSTHROUGH`, a comma list where
|
|
261
|
+
a trailing `*` makes an entry a prefix:
|
|
262
|
+
|
|
263
|
+
```sh
|
|
264
|
+
ARCHME_CHILD_ENV_PASSTHROUGH='CLAUDE_CODE_USE_BEDROCK,AWS_*' archme daemon restart
|
|
265
|
+
```
|
|
266
|
+
|
|
267
|
+
Likely names: `CLAUDE_CODE_USE_BEDROCK`, `AWS_*`, `CLAUDE_CODE_USE_VERTEX`,
|
|
268
|
+
`ANTHROPIC_VERTEX_PROJECT_ID`, `CLOUD_ML_REGION`, `GOOGLE_APPLICATION_CREDENTIALS`,
|
|
269
|
+
`ANTHROPIC_AUTH_TOKEN`, `ANTHROPIC_MODEL`, `SSL_CERT_FILE`, `XDG_*`.
|
|
270
|
+
|
|
271
|
+
- `archme daemon start`/`restart` bakes the setting **and the variables it
|
|
272
|
+
names, with their values at that moment** into the service unit, which is
|
|
273
|
+
written owner-only (`0600`); a restart also tightens an older unit. A prefix
|
|
274
|
+
entry is expanded then, so a variable you add later needs another restart.
|
|
275
|
+
A restart from a shell that lacks them keeps the unit's values;
|
|
276
|
+
`ARCHME_CHILD_ENV_PASSTHROUGH=` removes the setting and its variables.
|
|
277
|
+
- `ARCHME_*` and `SUPABASE_*` names (the daemon's own config) never pass,
|
|
278
|
+
even if listed, and a bare `*` is ignored.
|
|
279
|
+
- `archme doctor` prints the setting and the names it resolves to (never the
|
|
280
|
+
values), from the service unit or else your shell.
|
|
281
|
+
|
|
246
282
|
## What NOT to do
|
|
247
283
|
|
|
248
284
|
- **Don't fabricate anchors.** If you can't verify it via the CLI,
|