Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (clawdi) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

clawdi

iCloud for AI Agents. One CLI to share sessions, skills, memory, and vault secrets across Claude Code, Codex, OpenClaw, and Hermes — with an MCP server on the other end of the pipe.

Quickstart

# Try without installing
npx clawdi --help

# Or install globally
npm i -g clawdi          # or: bun add -g clawdi
clawdi auth login        # opens the dashboard in your browser to authorize
clawdi setup             # detect agents, register MCP, install skill
clawdi doctor            # verify everything's wired up

Headless? clawdi auth login --manual skips the browser and prompts for an API key from Settings → API Keys.

Requirements

Node ≥ 18
At least one supported agent installed on the machine (detected automatically)
Bun is only required if you ingest Hermes sessions (clawdi push --agent hermes) — bun:sqlite is loaded on demand.

Commands

Command	What it does
`clawdi auth login` / `logout`	Authenticate with the Clawdi Cloud backend
`clawdi status [--json]`	Show auth + per-module activity
`clawdi config list/get/set/unset`	Manage `~/.clawdi/config.json`
`clawdi setup [--agent <type>] [-y]`	Detect installed agents, register this machine, install built-in skill, wire up MCP
`clawdi teardown [--agent <type> --all --keep-skill --keep-mcp -y]`	Reverse setup: remove env file, bundled skill, and MCP entry
`clawdi push [--modules --since --project --all --agent --dry-run]`	Upload sessions / skills to the cloud
`clawdi pull [--modules --agent --dry-run]`	Download cloud skills to registered agents
`clawdi skill list [--json]`	List uploaded skills
`clawdi skill add <path> [-y]`	Upload a skill directory or single `.md` file (prompted preview)
`clawdi skill install <repo> [-a --agent] [-l --list] [-y]`	Install a GitHub skill into cloud and one or more agents
`clawdi skill rm <key>`	Remove a cloud skill
`clawdi skill init [name]`	Scaffold a new `SKILL.md` template
`clawdi memory list [--json --limit --category]`	List memories
`clawdi memory search <query> [--json --limit --category]`	Search memories by text
`clawdi memory add <content>` / `rm <id>`	Add or delete a memory
`clawdi vault set <key>` / `list [--json]` / `import <file>`	Manage secrets
`clawdi run -- <cmd>`	Run a command with vault secrets injected into env
`clawdi doctor [--json]`	Diagnose auth, agent paths, vault, MCP connectivity
`clawdi update [--json]`	Check for a newer CLI version
`clawdi mcp`	Start MCP server (stdio transport, for agents)

Run any command with --help to see its flags and real examples.

Environment variables

Variable	Purpose
`CLAWDI_API_URL`	Override the backend endpoint (production builds default to `https://cloud-api.clawdi.ai`; from-source dev defaults to `http://localhost:8000`)
`CLAWDI_DEBUG`	Print stack traces on errors
`CLAWDI_NO_UPDATE_CHECK`	Suppress the non-blocking update check
`CLAWDI_NO_AUTO_UPDATE`	Skip the default-on background auto-updater. Persistent equivalent: `clawdi config set autoUpdate false`
`CLAUDE_CONFIG_DIR`	Custom home for the Claude Code adapter (instead of `~/.claude`)
`CODEX_HOME`	Custom home for the Codex adapter (instead of `~/.codex`)
`HERMES_HOME`	Custom home for the Hermes adapter (instead of `~/.hermes`)
`OPENCLAW_STATE_DIR`	Custom OpenClaw state directory
`OPENCLAW_AGENT_ID`	Target a specific OpenClaw agent (default `main`)
`CI`, `GITHUB_ACTIONS`, `GITLAB_CI`, `CIRCLECI`, `TRAVIS`, `BUILDKITE`, `JENKINS_URL`, `TEAMCITY_VERSION`	Detected as CI; interactive prompts are disabled

Local state

Everything clawdi writes lives under ~/.clawdi/:

~/.clawdi/
├── config.json        user config (apiUrl)
├── auth.json          API key (mode 0600)
├── state.json         per-module last-activity timestamps
├── environments/      one file per registered agent
└── update.json        cached npm registry lookup

Corrupted state.json is tolerated with a warning, not a crash.

Troubleshooting

clawdi doctor         # a single-shot diagnostic

It verifies auth, API reachability, each known agent's install path, vault resolution, and MCP connector config — with actionable hints on every failing check.