DocsSupported Agents

Supported Agents

Blueprint Stack ships with 2 built-in agents and supports unlimited custom agents. You can switch between agents per session or run multiple agents in parallel across tabs. Selecting a different agent from the picker opens a new tab automatically. CLI and ACP adapter installs are manual; Blueprint Stack does not auto-download dependencies. Select an agent below for setup instructions.

AGENT_PICKER_BEHAVIOR

- Selecting a different agent from the picker opens a new tab for that agent.

- Your current chat tab is preserved, so you can keep multiple concurrent sessions (for example, one Claude Code tab and one Codex tab).

- Each agent in the picker shows a status label: Available, Not Installed, or Missing API Key.

# Built-in Agents

# Custom Agents

You can add unlimited custom ACP-compatible agents via Project Settings > Plugins > Blueprint Stack > Agents.

Custom agent configuration includes:

- Executable path -- Path to the agent binary or command name.

- Arguments -- Command-line arguments passed to the executable.

- Working directory -- Directory the agent process runs in.

- Environment variables -- Key-value pairs injected into the agent process.

- API key -- Optional authentication credential.

- Model ID -- Optional model identifier to pass to the agent.

- Install command -- Shell command shown to the user for installing the agent.

# Path Resolution

Blueprint Stack resolves agent executables by searching the following locations:

- System PATH

- npm global bin directory

- bun global bin directory

- cargo bin directory

- volta bin directory

- fnm bin directory

- asdf shims directory

- mise shims directory

- scoop shims directory

- Homebrew bin directory

# Status Labels

The agent picker shows a live status for each agent:

- Available -- The agent executable was found and is ready to use.

- Not Installed -- The agent executable was not found in any resolved path.

- Missing API Key -- The executable was found but authentication is not configured.