@candledottv/cli 0.11.4 → 0.11.6

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.
Files changed (3) hide show
  1. package/README.md +13 -3
  2. package/dist/index.js +37496 -34294
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -52,10 +52,10 @@ node packages/cli/dist/index.js auth login
52
52
  | Command | What it does |
53
53
  | --- | --- |
54
54
  | `candle setup [--no-browser]` | The onboarding wizard: authorizes this device (skipped when already authorized), prints the agent wallets as funding destinations plus the paste-into-your-agent brief, shows the skill/MCP install lines, runs the full doctor check (setup's exit code is doctor's), and links the web console. Safe to re-run. |
55
- | `candle auth login [--profile <name>] [--scopes <a,b,c>] [--label <name>] [--no-browser]` | Authorizes this device: prints a code, opens (or prints) an approval URL, polls until approved, then stores the resulting device token and API key. |
55
+ | `candle auth login [--profile <name>] [--scopes <a,b,c>] [--label <name>] [--no-browser]` | Authorizes this device: prints a code, opens (or prints) an approval URL, polls until approved, then stores the resulting device token and API key. `--label` names both the device and the key. |
56
56
  | `candle auth status` | Shows which storage backend is in use, both credential prefixes, the config file path, and a live validity check for each credential. |
57
57
  | `candle auth logout [--keep-key]` | Revokes the stored API key (skipped with `--keep-key`), clears local credentials and config, and prints the portal URL for revoking the device itself. |
58
- | `candle keys list` | Lists this account's API keys: prefix, scopes, environment, timestamps, and which device minted each one. |
58
+ | `candle keys list [--scopes]` | Lists this account's API keys: prefix, name, Read or Read:Write access, environment, timestamps, and which device minted each one. `--scopes` adds the raw scopes, sorted. |
59
59
  | `candle keys create [--scopes <a,b,c>] [--label <name>] [--expires-in <days>] [--tx-limit <usd> [--reset daily\|weekly\|monthly\|never]]` | Creates a new API key and prints the plaintext exactly once, with the same optional name, expiration, and USD transaction limit the portal's create form takes. Stored locally only if the CLI does not already hold a working key. |
60
60
  | `candle keys revoke <prefix>` | Revokes an API key by prefix. Revoking the CLI's own stored key also clears it locally. |
61
61
  | `candle wallets` | Shows the account's embedded (launch) wallets and any linked wallets, using the API key, with a `Signer` column saying whether this machine holds each linked wallet's signing key. |
@@ -108,9 +108,15 @@ grep candle-darwin-arm64 SHA256SUMS | shasum -a 256 -c
108
108
 
109
109
  ```
110
110
  gh attestation verify candle-darwin-arm64 --repo candledottv/agentic \
111
- --signer-workflow candledottv/agentic/.github/workflows/release.yaml
111
+ --cert-identity https://github.com/candledottv/agentic/.github/workflows/release.yaml@refs/tags/cli-v0.6.1
112
112
  ```
113
113
 
114
+ `--cert-identity` is the signing certificate's subject, the workflow file and the release tag in
115
+ one string, so it pins both: an attestation minted by the same workflow for a different tag does
116
+ not verify. Pass it on its own: `gh` treats its identity flags (`--cert-identity`, its regex form
117
+ and the two signer flags) as mutually exclusive, and the signer-workflow flag alone would accept
118
+ any tag's attestation.
119
+
114
120
  ```
115
121
  curl -fsSLO https://github.com/candledottv/agentic/releases/download/cli-v0.6.1/candle-darwin-arm64.sigstore.json
116
122
  cosign verify-blob --new-bundle-format --bundle candle-darwin-arm64.sigstore.json \
@@ -138,6 +144,10 @@ guarantee is unconfirmed: a wallet stop whose remote enforcement is still pendin
138
144
  enabled without verified signing authority, or a sweep that left a residual). Treat `3` as not
139
145
  done: follow the printed next step, usually re-running the same command.
140
146
 
147
+ The value is complete when the process exits, whatever stdout is connected to: a file, a pipe
148
+ into `jq`, a subprocess, or an MCP host. The CLI exits only after stdout has drained, and a
149
+ reader that closes the pipe early (`| head`) ends the output without an error.
150
+
141
151
  A failure envelope is `{ ok: false, code, message }`, with an optional one-line `suggestion` and,
142
152
  where a refusal carries facts worth acting on, an optional nested `details`. A vault that is not
143
153
  where the command looked answers with `details: { path, pathSource: "flag" | "env" | "default" }`,