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 +4 -3
- package/dist/index.js +185 -184
- package/dist/skills/clawdi/SKILL.md +5 -2
- package/package.json +1 -1
|
@@ -88,8 +88,11 @@ Connected service tools (Gmail, GitHub, Notion, etc.) are dynamically registered
|
|
|
88
88
|
|
|
89
89
|
When the user asks to migrate secrets into Clawdi Vault or script secret writes, prefer the CLI over raw HTTP calls:
|
|
90
90
|
|
|
91
|
-
- Use `clawdi vault set KEY --
|
|
92
|
-
- Use `clawdi vault
|
|
91
|
+
- Use `clawdi vault set KEY --prompt` for one-off manual secret entry; it prompts without echoing input.
|
|
92
|
+
- Use `clawdi vault set KEY --stdin` for piped values. Empty stdin is rejected unless `--allow-empty` is passed intentionally.
|
|
93
|
+
- Use `clawdi vault set KEY --value <value>` only when shell history exposure is acceptable.
|
|
94
|
+
- Use service-specific vault slugs such as `api-service/env/KEY`; avoid broad slugs such as `prod/KEY`.
|
|
95
|
+
- Use `clawdi vault import --vault <service-slug> --section <name> --project <project> --yes <file>` for non-interactive `.env` migrations into a section.
|
|
93
96
|
- Keep `.env` import keys as POSIX environment identifiers such as `OPENAI_API_KEY`; section names belong in `--section`, not inside the key name.
|
|
94
97
|
- Use `clawdi vault rm <vault>/<section>/<field> --yes` or `clawdi vault delete ...` to clean up misplaced keys.
|
|
95
98
|
- Prefer exact `clawdi://project/...` references printed by the CLI. Do not print plaintext secret values unless the user explicitly asks for them.
|