Agent Providers

Vect is a provider-agnostic IDE that wraps any AI coding agent CLI. It auto-detects installed agents via which and reads their native history and configuration formats.

Supported Agents

Claude Code

Install: see Claude Code documentation

Codex CLI

Install: npm install -g @openai/codex

OpenCode

Install: see the OpenCode repository

OpenCode is notable for supporting 75+ LLM models and storing history in SQLite rather than flat files. Reading that history needs the sqlite3 binary on your PATH; without it OpenCode sessions do not appear in the tree. The same applies to Hermes.

OpenCode does not ship an ACP server, so it can hold a session of its own but cannot be seated in a room.

Hermes

Install: see Hermes documentation

Hermes is Nous Research's model-agnostic, self-improving agent supporting 30+ providers.

How Vect Detects Agents

On startup, Vect runs which <binary> for each registered agent to check if the CLI is available on the system PATH. Detected agents appear in the session creation dropdown.

Agent Configuration

Each agent instance can be configured with:

• Custom environment variables: passed to the agent process via env record
• Binary override: use a specific path instead of the PATH-resolved binary
• Per-project instructions: Vect reads the agent's designated instructions file from the workspace root

Adding Custom Agents

The agent registry is defined in packages/shared/src/agent/registry.ts. Each agent definition specifies:

• id: unique identifier
• name: display name
• binary: CLI executable name
• detectCommand: how to check if installed (default: which)
• historySupported: whether Vect can read past sessions
• historyFormat: jsonl, json, sqlite, or none
• historyPath: where the agent stores conversation history
• configPath: agent configuration file location
• projectInstructionsFile: the markdown file the agent reads for project context