Create the hosted vault
Start with a free vault, seeded with bundled skills and the same validation gate used by local installs.
Use the hosted path when you want remote Streamable HTTP MCP, OAuth, role-aware access, bundled skills, and drift checks without standing up your own vault first.
The cloud flow should feel like the local installer: small surface area, no mystery setup, and the same MIT source available when you want to self-host.
Start with a free vault, seeded with bundled skills and the same validation gate used by local installs.
Point Claude Code, Codex, Cursor, AutoHub, or another MCP client at the remote Streamable HTTP endpoint.
Use OAuth and role-aware filtering so read-only users and owners see the right skill set.
Export, self-host, or run local-only later. Hosted launch is the shortest path, not a lock-in story.
The docs still teach local-first setup. The main action now speaks to the fastest path for new users: a free hosted vault on AutoVault hardware with a remote MCP endpoint they can connect from an agent.