vruum init

One command to wire Vruum into every detected AI coding harness — register the MCP, link skills, and write instruction files.

vruum init is the one-shot setup command. It detects every supported AI coding harness in the current project and, for each, does three things:

1. Registers the MCP — writes a static Authorization: Bearer config pointed at https://api.vruum.ai/mcp, reusing the token from vruum login. Bearer-first by design: it avoids the interactive-OAuth re-auth that drops hosted MCP connections mid-session.
2. Links the client-safe skills — makes the Vruum operator skills available to the harness.
3. Writes instruction files — drops harness-native instruction files that point the harness at the Operate Vruum guide.

vruum login                              # store your token first
vruum init                               # wire every detected harness
vruum init --project-dir /path/to/project

Each step is best-effort and independent: one failing step (or harness) never aborts the rest, so a single run gives you a full picture. Restart your harness afterwards to load the Vruum MCP, then verify with a real tool call.

The harnesses it wires

init ships adapters for seven AI coding harnesses and only touches the ones it detects in the project:

If no supported harness is detected, init tells you so and exits without writing anything.

Local-CLI only

init writes config files on your host, so it is deliberately not reachable through the server-side vruum_exec MCP tool (which injects your token and runs server-side). Run init from your local CLI, where it acts under your own host and credentials. See MCP for the vruum_exec blocked-command list.

See also

• Getting Started — install, login, init, first call.
• MCP — the curated tool set and how connections are authed.
• Auth — the token model init reuses.