@staff0rd/assist 0.495.0 → 0.496.1
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 +2 -2
- package/claude/settings.json +4 -0
- package/dist/commands/sessions/web/bundle.js +218 -218
- package/dist/index.js +68 -19
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -182,9 +182,9 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
|
|
|
182
182
|
- `assist run add` - Add a new run configuration to assist.yml and create a Claude command file
|
|
183
183
|
- `assist run link <path> --prefix <prefix>` - Link run configurations from another project's assist.yml
|
|
184
184
|
- `assist run remove <name>` - Remove a run configuration and delete its Claude command file
|
|
185
|
-
- `assist config get <key>` - Get a config value. Secret values (`database.url`, `roam.*` tokens, `sql.connections[].password`, `seq.connections[].apiToken`) print as `<hidden>`; `--reveal` prints the raw value undecorated for command substitution. An unset key still reports `Key "<key>" is not set`
|
|
185
|
+
- `assist config get <key>` - Get a config value. Secret values (`database.url`, `roam.*` tokens, `sql.connections[].password`, `seq.connections[].apiToken`) print as `<hidden>`; `--reveal` prints the raw value undecorated for command substitution and always needs an explicit permission prompt (the CLI hook never auto-approves it). An unset key still reports `Key "<key>" is not set`
|
|
186
186
|
- `assist config list` - List all config values, with secret values shown as `<hidden>` (no reveal option)
|
|
187
|
-
- `assist config set <key> <value>` - Set a config value. `--global` writes to `~/.assist.yml`; `-g --repo [name]` writes a per-repo override there
|
|
187
|
+
- `assist config set <key> <value>` - Set a config value. `--global` writes to `~/.assist.yml`; `-g --repo [name]` writes a per-repo override there. The confirmation line and any validation error mask secret values
|
|
188
188
|
- `assist config unset <key>` - Remove a config value so the key falls back to the global value or schema default (`-g` targets `~/.assist.yml`; `-g --repo [name]` removes it from a per-repo override there)
|
|
189
189
|
|
|
190
190
|
The Config tab of the sessions web dashboard never receives secret values: `GET /api/config` replaces each one with a set-or-unset marker, so a configured secret renders as a mask and an unset one as `not set`, both keeping their project/global/default chip. Secret fields edit write-only - the mask clears on focus, typing a value replaces the stored one, and leaving the field untouched keeps it.
|