Skip to content
vops

Client setup

The client adapter installs three kinds of integration: the canonical vops skill, the local MCP configuration and a small managed project bootstrap.

Detect clients and current state

Run from the application repository:

Terminal window
vops agent clients --project .

Each client is reported as:

  • absent — not detected;
  • found — detected but missing part of the vops integration;
  • ready — skill, MCP configuration and bootstrap validate.

vops agent status is an alias for the same validation:

Terminal window
vops agent status --project .

Project scope

Project scope is the recommended starting point:

Terminal window
vops agent setup codex --scope project --project .

Supported client IDs are:

  • codex;
  • claude-code;
  • opencode;
  • antigravity.

Configure every supported adapter when the repository is intentionally used with multiple clients:

Terminal window
vops agent setup all --scope project --project .

Project setup keeps the vops routing instructions close to the repository and avoids making infrastructure guidance globally active for unrelated work.

User scope

Terminal window
vops agent setup codex --scope user

Use user scope only when vops is a normal tool across many repositories. A user-scoped skill does not grant an infrastructure session; it only makes the knowledge and connection route available.

Safe merge behavior

Setup:

  • merges only the selected client’s configuration;
  • backs up an existing file before a material merge;
  • marks the bootstrap block vops owns;
  • is idempotent when repeated;
  • reports every changed and backup path.

Review those paths like any other project change. Client-specific files remain thin adapters; product policy does not live in four divergent configurations.

Remove the integration

Terminal window
vops agent uninstall codex --scope project --project .

Uninstall removes only vops-managed material and preserves unrelated client configuration.

Uninstalling the adapter does not revoke a session token already issued to a running process. Revoke the session separately.

After setup

Start at the lowest useful authority:

  1. validate vops agent status;
  2. restart the client if it loads MCP configuration only at launch;
  3. ask a product-knowledge question;
  4. verify public capability discovery;
  5. create a bounded session only when private inventory or an operation is actually needed.