clawdi 0.8.6 → 0.10.0

package/dist/skills/clawdi/SKILL.md

@@ -12,7 +12,7 @@ You have access to Clawdi Cloud tools via the `clawdi` MCP server. Use them aggr
 Three tools for cross-agent memory:
 
 - `memory_search` — Search long-term memory by natural-language query (any language).
-- `memory_add` — Save a durable memory for cross-agent recall. Categories: `fact` (technical facts, API details, config values), `preference` (user preferences, coding style, workflow choices), `pattern` (recurring patterns, pitfalls, team conventions), `decision` (architecture decisions and their reasoning), `context` (project context, deadlines, ongoing work).
+- `memory_add` — Save a durable memory for cross-agent recall. Do not store plaintext tokens, API keys, or bearer credentials; store those in Vault and save only the `clawdi://` reference. Categories: `fact` (technical facts, API details, config values), `preference` (user preferences, coding style, workflow choices), `pattern` (recurring patterns, pitfalls, team conventions), `decision` (architecture decisions and their reasoning), `context` (project context, deadlines, ongoing work).
 - `memory_extract` — Batch-extract durable memories from the CURRENT conversation. Call this when the user says "extract memories", "save what we discussed", "remember this conversation", or equivalent. The tool returns instructions that walk you through a list-then-confirm flow using `memory_search` and `memory_add` — follow them exactly, including **waiting for the user's approval before writing anything**. Never skip the confirmation step, never save more than 5 memories in one invocation, and do not narrate your internal workflow to the user.
 
 ### When to search — bias toward calling
@@ -46,6 +46,8 @@ Write memories as standalone sentences with full context — include names, not
 
 Do NOT save trivial facts that are obvious from the code itself, or generic programming knowledge.
 
+Do NOT save plaintext tokens, API keys, bearer credentials, or private keys in memory. Use Vault for secret values and save only a `clawdi://` reference when future agents need to know where a secret lives.
+
 ## Sessions
 
 Two tools for reading and finding past agent conversations stored in Clawdi Cloud:
@@ -94,5 +96,7 @@ When the user asks to migrate secrets into Clawdi Vault or script secret writes,
 - Use service-specific vault slugs such as `api-service/env/KEY`; avoid broad slugs such as `prod/KEY`.
 - Use `clawdi vault import --vault <service-slug> --section <name> --project <project> --yes <file>` for non-interactive `.env` migrations into a section.
 - Keep `.env` import keys as POSIX environment identifiers such as `OPENAI_API_KEY`; section names belong in `--section`, not inside the key name.
-- Use `clawdi vault rm <vault>/<section>/<field> --yes` or `clawdi vault delete ...` to clean up misplaced keys.
+- Use `clawdi vault attach <vault> --project <project>` to make an existing Vault available in another Project.
+- Use `clawdi vault detach <vault> --project <project>` to remove one Project's access without deleting keys.
+- Use `clawdi vault rm <vault>/<section>/<field> --global --yes` only when the key should be deleted from the shared Vault for every attached Project.
 - Prefer exact `clawdi://project/...` references printed by the CLI. Do not print plaintext secret values unless the user explicitly asks for them.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "clawdi",
-	"version": "0.8.6",
+	"version": "0.10.0",
 	"description": "iCloud for AI Agents — cross-agent sessions, skills, memory, and vault.",
 	"license": "MIT",
 	"type": "module",
@@ -59,6 +59,7 @@
 		"commander": "^13.0.0",
 		"openapi-fetch": "^0.17.0",
 		"tar": "^7.5.13",
+		"yaml": "^2.9.0",
 		"zod": "^4.3.6"
 	},
 	"devDependencies": {