Configuration

Authenticate

Sign in once:

vscan auth

vscan opens your browser for OAuth. After sign-in, future scans, model commands, usage checks, and MCP runs use the saved session.

If a command says authentication is required, run vscan auth again.

Model

The active model determines which Vaktex model handles future scans. Most users can keep the default. Change it when you are testing a different model or your organization recommends one for a particular workflow.

View or choose the active model:

vscan model

Set a model directly:

vscan model <id>

The active model is used for normal scans, JSONL scans, and MCP scans until you change it again.

Account and Features

Check your current account, organization, feature availability, and local dependencies:

vscan about

This is the quickest way to confirm that the CLI is signed into the organization you expect before running a scan.

MCP Setup

Install MCP configuration for a supported coding agent:

vscan mcp init

The installer prompts for the package manager and host to configure. After setup, the host can start the vscan MCP server when it needs it.

Requirements

Standard scans require Node.js 18 or newer. Optional workflows may also use Git, Docker, or a local Git hosting CLI depending on what you ask vscan to do.

Use vscan about to see what is available on your machine.