Clawdi

Clawdi Cloud

Use Clawdi Cloud tools through the clawdi MCP server. Treat the live tool schemas as authoritative.

Hosted Boundary

Third-party tool routing below applies unchanged in Hosted. Do not inspect, run, or suggest Clawdi host-management commands such as clawdi setup, clawdi wallet, clawdi vault, or clawdi ai-provider. Do not use any clawdi CLI command as a Cloud capability fallback; use the Clawdi MCP tools exposed to the Hosted runtime.

Context Routing

Use the current conversation and user-provided artifacts first. For project facts, inspect the workspace, repository documentation, and local history. Use memory_search only for missing user-specific preferences, decisions, or prior context. Use session_list, session_search, and session_get only when the user asks for past conversations or transcript-level detail is necessary. Do not call Memory and Session speculatively or in parallel. A named entity alone does not justify a Cloud lookup, and an empty Memory result does not justify a Session search.

Memory

Memory is shared across the user's Hosted agents, not isolated to the current agent.

• memory_search — Search durable memory by natural-language query.
• memory_list — Review stored memories and their stable IDs.
• memory_create — Save a durable fact, preference, pattern, decision, or project context.
• memory_update — Replace one exact memory's content without changing its metadata.
• memory_delete — Delete one exact memory by ID.
• memory_extract — Prepare memories from the current conversation. Follow its returned review-and-confirm instructions and wait for user approval before calling memory_create.

Use memory_create for explicit "remember this" requests or durable user-specific preferences and decisions not discoverable from the repository. Ask when persistence is unclear. Do not save routine task completion, code facts, speculation, or plaintext secrets; use Vault and remember only the exact clawdi:// reference. List before updating or deleting unless the user already supplied the exact memory ID; never infer which stored item to mutate.

Sessions

• Use session_list to browse recent sessions or filter by time, Agent, or Project.
• Use session_search to find past agent conversations by keyword and obtain session UUIDs.
• Use session_get to read a session by UUID or Clawdi share URL.
• Use session_share_create to publish an immutable snapshot only when the user explicitly asks to share a Session, part of it, or one Assistant response.
• Use session_share_list to inspect active links and obtain their exact IDs and kinds.
• Use session_share_revoke to stop sharing one exact link only when the user asks.

Call session_get when the user provides a Clawdi share URL or session UUID and wants its contents. Use session_search to locate a requested unnamed conversation. Do not use a generic web fetcher for Clawdi share URLs.

For session_share_create, omit position for the full session scope. For through or response, use the stable message position returned by session_get or session_search, never a filtered array index; response must target an Assistant message. Public snapshots include only the existing safe user/Assistant projection, never reasoning, system/developer messages, hidden events, or tool activity. Before revoking, use session_share_list unless the user already supplied the exact share_id and kind; never infer a link ID or kind. Hosted Session sharing uses these MCP tools only, not CLI commands.

Projects

• project_current_get — Read the runtime-bound Project.
• project_list — List Projects visible to the caller.
• project_get — Read one visible Project by UUID.

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.

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:

• clawdi://project/<project-id>/vault/<vault>/field/<field>
• clawdi://project/<project-id>/vault/<vault>/section/<section>/field/<field>

Vault write tools are available for explicit user requests:

• 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 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 new or updated credentials

Use vault_request_create with exact project_id, vault_id, canonical slug, optional section, and a batch of Vault field names in fields. A Vault is a key bundle: request related new and existing keys together under one link. Include existing keys only when the user authorized updating them; do not delete them first. Existing Vault values remain unchanged until successful submission and are never shown or prefilled. Overlapping pending requests are rejected; a change to any requested field conflicts with the entire batch. Show the returned url unchanged to the user; do not ask them to paste secrets into chat. Opening the link does not consume it. The user can add fields or import a pasted/uploaded .env on the page, preview replacements, and apply them to the same form. Original requested names remain mandatory; only the user chooses extras after link creation (32 fields total). Saving the entire form consumes the link once. Selected fields must still match creation state, and extras cannot overlap another pending request. Status includes saved extras and their exact references; never assume only the originally requested names were saved.

Check vault_request_status with its request_id after the user finishes. pending is not a secret value; supplied means the exact references are ready. On expired or conflict, inspect current Vault metadata and reassess the authorized fields before creating a fresh request; do not blindly retry an overwrite. 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 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 vault_request_status reports supplied, match its Vault ID, section and field names in the index and require the local Vault content_version to be at least the status content_version. The API requires this counter; existing names alone do not prove delivery. If the owned index is incomplete or behind, wait for runtime reconciliation and report unverified delivery. Do not read secret values to check freshness. Pending requests are metadata only, never empty pseudo-secrets. 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.