clawdi 0.8.2 → 0.8.4

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 CHANGED
@@ -90,8 +90,9 @@ Later, in a different agent or a fresh session, ask "what package manager should
90
90
  Run a fullstack dev command with vault references without putting plaintext secrets on disk:
91
91
 
92
92
  ```bash
93
- printf '%s\n' "$OPENAI_API_KEY" | clawdi vault set OPENAI_API_KEY --stdin
94
- clawdi vault import --vault prod --section stripe --project personal --yes .env.stripe
93
+ clawdi vault set OPENAI_API_KEY --prompt
94
+ printf '%s\n' "$OPENAI_API_KEY" | clawdi vault set api-service/env/OPENAI_API_KEY --stdin
95
+ clawdi vault import --vault api-service --section stripe --project personal --yes .env.stripe
95
96
  echo "OPENAI_API_KEY=clawdi://project/<project-id>/vault/default/field/OPENAI_API_KEY" > .env.clawdi
96
97
  clawdi run --dry-run --env-file .env.clawdi -- npm run dev
97
98
  clawdi run --env-file .env.clawdi -- npm run dev
@@ -100,7 +101,7 @@ clawdi inject --dry-run --in .env.clawdi --out .env.local
100
101
  clawdi inject --force --in .env.clawdi --out .env.local
101
102
  ```
102
103
 
103
- `clawdi vault set`, `clawdi vault import`, `clawdi vault rm`, and `clawdi vault list` print the concrete Project target or exact references that include the Project ID. `vault set` supports `--value` and `--stdin` for scripts; `vault import` supports `--vault`, `--section`, `--project`, and warns about skipped invalid dotenv identifiers. Project-relative references such as `clawdi://default/OPENAI_API_KEY` still work for portable templates, but exact references are the default copy/read UX.
104
+ `clawdi vault set`, `clawdi vault import`, `clawdi vault rm`, and `clawdi vault list` print the concrete Project target or exact references that include the Project ID. `vault set` supports `--prompt` for secure one-off entry, `--stdin` for scripts, and `--value` when shell history exposure is acceptable; empty stdin is rejected unless `--allow-empty` is passed intentionally. `vault import` supports `--vault`, `--section`, `--project`, and warns about skipped invalid dotenv identifiers. Prefer service-specific vault slugs such as `api-service` over broad environment slugs such as `prod`. Project-relative references such as `clawdi://default/OPENAI_API_KEY` still work for portable templates, but exact references are the default copy/read UX.
104
105
 
105
106
  Agents should prefer `clawdi run --env-file .env.clawdi -- <command>` when they can launch the tool themselves. Use `clawdi inject` only for tools that must read a physical `.env.local`; generated files are written owner-only and should stay gitignored.
106
107