Skip to main content

BoxOwl developers

Welcome. This portal covers everything you need to build with the Pillar 3 surface of BoxOwl — the local-first vault daemon, the per-tool scope grammar, the MCP transport, the audit log, the SDKs, and the skill catalog.

If you're new, head to the Quickstart — five minutes from brew install to a working MCP tool call from your agent host of choice.

The personal stack​

BoxOwl is the user-owned personal stack — three pillars on one architecture:

PillarSurfaceAudience-facing page
1 — Secretspasswords, payment methods, secure notes, autofillpasswords
2 — Personal Dataname, address, identity, work history; SSoT + propagationpersonal-data
3 — Personal AIvault + scope grammar + audit; MCP + per-host walkthroughspersonal-ai

This developer portal documents the Pillar 3 surface. Pillar 1 and Pillar 2 share the same vault and audit substrate; their dev-facing API lives at api.boxowl.me and is reachable from your daemon-connected agent under the same scope grammar.

Where to start​

  • Quickstart — install daemon → install skill → first MCP tool call. ~5 minutes.
  • Concepts — the three-pillar architecture, the local vault, the scope grammar, the audit log, the Hermes Agent pairing.
  • Daemon — boxowl-daemon CLI reference + MCP transport + REST surface.
  • Agent hosts — Claude Desktop · Claude Code CLI · Cursor · VS Code Copilot · ChatGPT · Hermes · Gemini CLI · OpenClaw.
  • Skills — the @boxowl/skills installer and the bundle catalog.
  • SDKs — @boxowl/sdk browser bootstrap, @boxowl/node, @boxowl/react.
  • API — REST surface for PDaaS + SMRT + the OpenAPI spec.
  • Troubleshoot — the targets every boxowl-daemon doctor failure cites.

Open source​

The pieces you run on your machine are all Apache 2.0:

Cloud backend + Android app + browser extension are closed source today; the substrate the user runs is open.