Install AutoVault.
One command. No daemon.
Create the local vault, admit a signed skill, scope it to the agents that need it, and run the same capability from Claude Code, Codex, or Cursor without maintaining forks.
Step 1 — Install the local vault
Pick any channel; each installs the same published CLI release. npm is the fastest path for Node 24+ environments, Homebrew is convenient on macOS, and the shell installer additionally provisions ~/.autovault, preserves it as user-owned storage, and bootstraps bundled skills unless AUTOVAULT_NO_BOOTSTRAP=1 is set. Nothing runs as a background daemon; local MCP hosts spawn stdio on demand.
# Node 24+: install the published npm package
$ npm install -g @autoworks-ai/autovault
# Or run the installer script end-to-end
$ curl -fsSL https://autovault.sh | sh
# macOS: also available through the tap
$ brew install autoworks-ai/tap/autovault
$ autovault skill list
Agent-assisted setup
If you want Claude Code to configure its own AutoVault bootstrap skill, give it this prompt. The hosted skill is a raw SKILL.md; the agent should fetch it, show you the behavior, install it locally only after approval, then run it.
Fetch https://autovault.dev/skill.md, show me what it will do, install it into ~/.claude/skills/autovault-bootstrap/SKILL.md if approved, then run /autovault-bootstrap.
autovault doctor and autovault sync-profiles --discover.Step 2 — Run the setup wizard
After install, autovault setup scans the vault, the bundled skills root, and any discovered native agent skill roots (~/.claude/skills, ~/.codex/skills, ~/.cursor/skills), then asks you per skill how to adopt it. Re-run any time to re-scan.
$ autovault setup --review
autovault setup to finish onboarding. If your existing ~/.claude/skills didn't import, pick the backup adoption mode (not the augment default). See Troubleshooting for the full recovery.Step 3 — Verify the install
One command confirms the binary, local vault folder, profile discovery, and signing key are ready before any skill enters the vault.
Step 4 — Add a skill source
autovault add accepts local paths, GitHub identifiers or URLs, agentskills slugs, and direct SKILL.md URLs. Every source runs through the same validation, signing, provenance, and profile-sync gate.
$ autovault add ./skills/skill-author --sync-profiles --yes
The vault is a folder
The final model is intentionally boring: a regular folder on disk. This is the current implementation layout: SQLite index, local signing key, source skills, source metadata, signed manifests, rendered variants, and profile links. Select a row to inspect how the folder is read.
Step 5 — Sync it to local agents
Profile sync projects admitted skills into agent-native roots while preserving user-managed files on conflict. Visibility comes from skill metadata plus optional named profiles in profiles.config.json; remote clients should read through MCP instead of expecting local symlinks.
$ autovault sync-profiles --discover
Step 6 — Run it from your agent
The same skill is now validated, scoped, and rendered for each target agent. The skill name stays stable, while tool names are transformed to match the caller.
> use skill-author to draft a new SKILL.md
✓ tool resolved: Read, Edit, Write
# extracting...
"This 24-page report covers Q1 platform metrics, with three..."
Remove a skill cleanly
If a skill no longer belongs in the vault, remove it through AutoVault rather than deleting folders by hand. The command deletes the vaulted copy and its vault-local transforms, refreshes generated profiles, and prunes AutoVault-managed symlinks from discovered native agent roots.
$ autovault remove skill-author
# automation-friendly output
$ autovault remove skill-author --json
--no-discover only when you intentionally want to leave discovered native host roots untouched. Use --link agent=/path/to/skills for a custom profile root.