clawdi 0.14.72 → 0.14.74

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "clawdi",
-	"version": "0.14.72",
+	"version": "0.14.74",
 	"description": "The best home for all your AI agents. Run them in the cloud or connect your own—with their context and tools in one place.",
 	"license": "MIT",
 	"type": "module",
@@ -11,7 +11,6 @@
 	"files": [
 		"bin",
 		"dist",
-		"runtime-mcp",
 		"egress-addon/clawdi_egress_addon.py",
 		"skills",
 		"LICENSE",
@@ -25,17 +24,16 @@
 	},
 	"scripts": {
 		"dev": "bun run src/index.ts",
-		"build": "bun run build:mcp && rm -rf dist && bun build src/index.ts --outdir dist --target node --minify --define 'process.env.CLAWDI_DEFAULT_API_URL=\"https://cloud-api.clawdi.ai\"' --define 'process.env.CLAWDI_DEFAULT_DEPLOY_API_URL=\"https://api.clawdi.ai\"'",
-		"build:mcp": "bun build ../runtime-mcp/src/index.ts --outdir runtime-mcp --target node --minify",
+		"build": "rm -rf dist && bun build src/index.ts --outdir dist --target node --minify --define 'process.env.CLAWDI_DEFAULT_API_URL=\"https://cloud-api.clawdi.ai\"' --define 'process.env.CLAWDI_DEFAULT_DEPLOY_API_URL=\"https://api.clawdi.ai\"'",
 		"build:native": "bun run scripts/build-native.mjs",
 		"build:native-release": "bun run scripts/build-native-release.mjs",
 		"package:native-release": "bun run scripts/package-native-release.mjs",
-		"build:dev": "bun run build:mcp && rm -rf dist && bun build src/index.ts --outdir dist --target node",
+		"build:dev": "rm -rf dist && bun build src/index.ts --outdir dist --target node",
 		"check:publish-manifest": "node scripts/check-publish-manifest.mjs",
 		"check:native-release": "bun run scripts/check-native-release.mjs",
 		"typecheck": "tsc --noEmit",
 		"test": "../../scripts/test.sh cli",
-		"test:internal": "bun run build:mcp && bash scripts/test-internal.sh",
+		"test:internal": "bash scripts/test-internal.sh",
 		"test:e2e": "../../scripts/test.sh cli tests/e2e",
 		"test:native-linux-lifecycle:internal": "CLAWDI_NATIVE_BINARY=${CLAWDI_NATIVE_BINARY:-dist-native/linux-x64/clawdi} bun test tests/e2e/native-installer.e2e.test.ts tests/e2e/native-daemon.e2e.test.ts",
 		"test:watch:local": "bun test --watch",
@@ -66,7 +64,6 @@
 	"devDependencies": {
 		"@clack/prompts": "^1.7.0",
 		"@clawdi/shared": "workspace:*",
-		"@clawdi/runtime-mcp": "workspace:*",
 		"@modelcontextprotocol/sdk": "^1.30.0",
 		"@types/bun": "^1.4.0",
 		"@types/node": "^24.13.3",

package/skills/clawdi/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: clawdi
-description: "Use Clawdi Cloud for missing user memory, past sessions, Project or Vault context, Clawdi share URLs, and connected-service fallback such as Gmail, GitHub, Notion, Drive, or Calendar. Prefer an authenticated official service CLI; otherwise choose a trusted direct MCP, safely installable official CLI, official API or SDK, or the Clawdi connector as fallback. Do not invoke solely because a project, person, repo, or tool is named."
+description: "API keys, tokens, memory, sessions, Projects, integrations. Use Clawdi Cloud when a task needs passwords or safe credential storage/provision, missing user memory or Project/Vault context, past conversations, Clawdi share URLs, or connected-service fallback such as Gmail, GitHub, Notion, Drive, or Calendar. Do not invoke solely because a project, person, repo, or tool is named."
 ---
 
 # Clawdi Cloud
@@ -80,19 +80,22 @@ an access boundary as well as a possible unknown UUID; never bypass it with anot
 
 ## Vault
 
+Vault stores credentials for authorized tools and services; it is not a universal service
+alternative. Reuse ready, authorized mechanisms before requesting missing credentials. An
+already-connected, capable Composio integration does not require duplicate credentials in Vault
+or account migration. Request credentials only when the chosen task path actually needs them.
+
 Vault read tools expose metadata and exact references:
 
 - `vault_list` — List Vault attachments and key counts for visible Projects.
 - `vault_get` — List key names, provenance, and exact `clawdi://` references for one attached Vault.
 
-Honor the user-selected Vault or existing local binding first; never silently switch
-sources. Otherwise inspect `vault_list` / `vault_get` metadata and reuse a Vault matching
-the task's purpose and intended access. Create in the current Workspace only when none
-is appropriate and creation is within the authorized task. Ask for the exact target only
-when ambiguity affects purpose or access. Linked Vaults can be synced read-only; do not
-request or modify fields outside the write boundary, or create duplicates to bypass access.
+Honor an explicit Vault/source or known local mapping first. Otherwise use `vault_list` /
+`vault_get` metadata to reuse a Vault suited to the task's purpose and access. Create in
+your own Workspace only when none is appropriate and the task authorizes creation.
+Clarify ambiguous sources; never create duplicates or write to linked Projects to bypass access.
 
-Use `vault_sync` to save credentials locally for task use. The metadata tools return
+Use `vault_resolve` only when the authorized task requires plaintext. The metadata tools return
 key names and exact references, never secret values. Preserve those references when
 passing them to an authorized runtime:
 
@@ -130,24 +133,38 @@ If submission times out, inspect status before repeating a mutation.
 
 ### Save and refresh credentials locally
 
-After a request is `supplied`, use `vault_sync` to save credentials locally by default.
-Every call requires `path`: choose a supported env filename in this Agent's authenticated
-workspace based on project conventions and Vault purpose, such as `.env.stripe` or
-`stripe.env`, without routine user reconfirmation. Report the chosen path. A file without
-a binding also requires `project_id`, `vault_id`, and optional `section`. Omit `section`
-for the entire Vault; an empty string selects unsectioned fields. If sections reuse names,
-select one section per file. The target must be untracked, Git-ignored, and not a symlink.
-Check only file/path metadata when choosing a target; never read env contents into the
-conversation. Let `vault_sync` reuse the binding internally and reject local conflicts.
-
-Before later task use, call `vault_sync` with the same explicit `path` when a refresh is
-needed; omit source arguments to reuse that file's durable binding. It adds, updates
-and deletes managed fields while preserving unrelated assignments. Conflicting sources
-or local edits stop the write; restore the managed assignment or choose a new file.
-Return only file path, status and counts; never print keys or the file, log secrets, or
-save them to Memory. Sync does not upload local edits, run in the background, or reload
-a running process's environment. It requires the standalone local MCP adapter; remote-only
-HTTP cannot write files. Do not invent a CLI fallback or script synchronization.
+Hosted runtime supplies `.clawdi/vaults/` under the native workspace automatically.
+Connected macOS/Linux/WSL Agents receive the same layout only in the workspace explicitly
+confirmed by setup. Use that configured path, which may differ from the current repository;
+do not guess from HOME, daemon CWD, or scanned sessions. Existing registrations without a
+Vault workspace do not download values. Native Windows daemon/file delivery is unsupported.
+
+Inspect only the configured `.clawdi/vaults/index.json` to select the intended Vault/section.
+Load its JSON file inside the authorized process or SDK without printing values or returning
+them to model/tool-result context merely to save them. These are generated files: do not
+edit, move or commit them. Hosted agents must not invoke/install the tenant Clawdi CLI.
+Connected operators configure delivery with `clawdi setup --agent <type> --vault-workspace <path>`;
+that changes only the Vault destination, never every repository scanned by the daemon.
+
+After a credential request is supplied, wait for the expected fields in index metadata before
+claiming delivery. If delivery is unavailable, report that state and any missing workspace
+binding instead of inventing a destination. Preserve unrelated local configuration.
+
+### Optional CLI environment files
+
+For an explicit operator-run compatibility workflow outside Hosted, use the available CLI.
+Choose a target outside the generated `.clawdi/vaults` directory:
+
+```bash
+clawdi vault materialize --vault <vault-uuid> --project <project-uuid> --out /absolute/project/.env
+clawdi vault pull --out /absolute/project/.env
+```
+
+The first command binds the exact source; later pulls reuse it and preserve unrelated
+assignments. Optional `--section <name>` selects one section. Files must be untracked,
+Git-ignored, and not symlinks. Source changes and local edits fail without overwriting.
+Report only the path, status, and counts. This does not upload local edits, run in the
+background, or reload a running process's environment.
 
 For explicit import/write, pass fields to `vault_item_upsert`; use
 `vault_item_delete` for exact batch deletions. Never upload local edits automatically.
@@ -167,7 +184,10 @@ already exposed by the runtime, and authorized API or SDK credentials. If an ins
 authenticated official CLI can perform the task, use it directly. Check availability and
 authentication non-destructively and prefer structured output.
 
-Otherwise choose the lowest-setup reliable option for the task. Consult the service's official
+Otherwise reuse a ready, authorized direct integration when it can perform the task. If none
+is usable and Composio is already connected and capable, use it without demanding a new key,
+login, installation, or account migration merely to avoid the connector. For remaining setup
+choices, choose the lowest-setup reliable option for the task. Consult the service's official
 documentation when installation, authentication, commands, or schemas are uncertain or likely
 to have changed:
 
@@ -177,7 +197,7 @@ to have changed:
   official, and no elevation or persistent host change is required.
 - Use the official API or SDK with a verified contract and credentials already authorized for
   the runtime, including through an exact Vault reference.
-- Use the Clawdi connector when no direct option can perform the operation.
+- Use the Clawdi connector when no direct option is usable for the operation.
 
 Before a side effect, establish the exact service account and organization, Project, or tenant.
 Use connection details from Composio discovery, or explicitly list accounts with

package/skills/hosted-versions/1/clawdi/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: clawdi
-description: "Use Clawdi Cloud for missing user memory, past sessions, Project or Vault context, Clawdi share URLs, and connected-service fallback such as Gmail, GitHub, Notion, Drive, or Calendar. Prefer an authenticated official service CLI; otherwise choose a trusted direct MCP, safely installable official CLI, official API or SDK, or the Clawdi connector as fallback. Do not invoke solely because a project, person, repo, or tool is named."
+description: "API keys, tokens, memory, sessions, Projects, integrations. Use Clawdi Cloud when a task needs passwords or safe credential storage/provision, missing user memory or Project/Vault context, past conversations, Clawdi share URLs, or connected-service fallback such as Gmail, GitHub, Notion, Drive, or Calendar. Do not invoke solely because a project, person, repo, or tool is named."
 ---
 
 # Clawdi Cloud
@@ -57,17 +57,29 @@ generic web fetcher for Clawdi share URLs.
 - `project_list` — List Projects visible to the caller.
 - `project_get` — Read one visible Project by UUID.
 
-A Hosted runtime is restricted to its bound Project. Treat not-found as an access boundary
-as well as a possible unknown UUID; do not try to bypass it through another tool.
+Strict-v2 Hosted runtimes can read their own Workspace and explicitly linked Projects
+that remain readable by the owner. `project_current_get` returns that Workspace; writes,
+new Vaults, and credential requests are limited to it. Legacy Agent-bound keys retain
+their narrower bound-Project read scope. Treat not-found as an access boundary as well
+as a possible unknown UUID; do not bypass it through another tool.
 
 ## Vault
 
+Vault stores credentials for authorized tools and services; it is not a universal service
+alternative. Reuse ready, authorized mechanisms before requesting missing credentials. An
+already-connected, capable Composio integration does not require duplicate credentials in Vault
+or account migration. Request credentials only when the chosen task path actually needs them.
+
 - `vault_list` — List attached Vaults and key counts for visible Projects.
 - `vault_get` — List key names, provenance, and exact references for an attached Vault.
 
-Use `vault_resolve` only when the current task requires one referenced plaintext value. Pass
-the exact Project-scoped reference. Treat the result as sensitive: never echo it, save it to
-Memory, or include it in logs.
+Honor an explicit Vault/source or known local mapping first. Otherwise use `vault_list` /
+`vault_get` metadata to reuse a Vault suited to the task's purpose and access. Create in
+your own Workspace only when none is appropriate and the task authorizes creation.
+Clarify ambiguous sources; never create duplicates or write to linked Projects to bypass access.
+
+Use `vault_resolve` only for authorized credential use, with exact Project-scoped
+reference(s) following its live schema. Never echo values, save them to Memory, or log them.
 
 The metadata tools never return plaintext secret values. Preserve exact references for
 `vault_resolve` or when passing them to an authorized runtime:
@@ -77,15 +89,15 @@ The metadata tools never return plaintext secret values. Preserve exact referenc
 
 Vault write tools are available for explicit user requests:
 
-- `vault_create` — Create a Vault attached to the runtime-bound Project.
+- `vault_create` — Create a Vault attached to your own Workspace.
 - `vault_item_upsert` — Create or replace exact fields in an attached Vault.
 - `vault_item_delete` — Delete exact fields from a single-Project Vault.
 
 Follow the live schema and supply every required Project, Vault, section, and field identity;
 never infer an overwrite or deletion. Treat field values as sensitive inputs and never echo
-them, save them to Memory, or include them in logs. Hosted writes are restricted to the
-runtime-bound Project, and field deletion is rejected when a Vault is attached to multiple
-Projects. Whole-Vault deletion, attach/detach, bulk import, and credential profiles remain
+them, save them to Memory, or include them in logs. Hosted writes are restricted to their
+own Workspace (the runtime-bound Project). Field deletion is rejected when a Vault is
+attached to multiple Projects. Whole-Vault deletion, attach/detach, and credential profiles remain
 unavailable through Agent MCP; do not bypass that boundary through raw HTTP.
 
 ### Request missing credentials
@@ -102,10 +114,29 @@ inspect the Vault and request only still-missing fields; never replace an existi
 retry. If creation times out, use `vault_get` to find recent request IDs before retrying.
 If submission times out, inspect status before repeating a mutation.
 
-Use `vault_resolve` for authorized runtime reads after supply. The returned `local_command`
-is guidance for a self-managed CLI installation, not an available hosted command. This
-runtime does not expose the CLI Vault-file binding/pull workflow; do not invent a local sync
-command or promise durable local environment synchronization here.
+### Use runtime-supplied credentials
+
+Clawdi runtime synchronizes readable Vaults from your own Workspace and explicitly linked,
+still-readable Projects into `.clawdi/vaults/` beneath your native workspace. Inspect only
+`.clawdi/vaults/index.json` for Vault IDs, section names, exact references, field names and files.
+Each section has a separate JSON file; equal field names in different sections stay separate.
+Select by the user's intended Vault and section, never by an ambiguous field name alone.
+
+Load the selected JSON file inside the authorized process or SDK without printing values.
+For example, Python can use `json.load(open(path))` and pass the selected key directly to
+its SDK. Do not read plaintext into model/tool-result context merely to save or copy it.
+Do not invoke or install the Clawdi CLI from the tenant. Runtime owns these generated files:
+do not edit, chmod, move, commit, or create your own files in `.clawdi/vaults/`. Preserve
+unrelated configuration in its `.clawdi` parent. Connected installations use this same
+layout on macOS/Linux only after an explicit workspace binding; do not assume an arbitrary
+repo is bound. Files remain readable by authorized programs running as the same user.
+
+After a credential request is supplied, inspect index metadata for the requested fields.
+Pending requests are metadata only, never empty pseudo-secrets. If delivery is delayed,
+report that state without claiming the credentials are saved. Runtime refreshes files;
+already-running processes must explicitly reload them. Offline delivery retains last good
+files; confirmed access removal removes generated files. Authorized code can read these
+files, so do not claim that subsequent plaintext exposure is impossible.
 
 ## Connector Routing
 
@@ -114,7 +145,10 @@ already exposed by the runtime, and authorized API or SDK credentials. If an ins
 authenticated official CLI can perform the task, use it directly. Check availability and
 authentication non-destructively and prefer structured output.
 
-Otherwise choose the lowest-setup reliable option for the task. Consult the service's official
+Otherwise reuse a ready, authorized direct integration when it can perform the task. If none
+is usable and Composio is already connected and capable, use it without demanding a new key,
+login, installation, or account migration merely to avoid the connector. For remaining setup
+choices, choose the lowest-setup reliable option for the task. Consult the service's official
 documentation when installation, authentication, commands, or schemas are uncertain or likely
 to have changed:
 
@@ -124,7 +158,7 @@ to have changed:
   official, and no elevation or persistent host change is required.
 - Use the official API or SDK with a verified contract and credentials already authorized for
   the runtime, including through an exact Vault reference.
-- Use the Clawdi connector when no direct option can perform the operation.
+- Use the Clawdi connector when no direct option is usable for the operation.
 
 Before a side effect, establish the exact service account and organization, Project, or tenant.
 Use connection details from Composio discovery, or explicitly list accounts with