Skip to content

ACP Pro · VS Code · Agent Client Protocol

One ACP Client for every AI agent.Sessions stay visible when you step away.

Open Claude Code, Codex, Copilot, Gemini, and other ACP agents side by side. Keep each task's model, permissions, working directory, git state, and history in its own tab—then open the live workspace in a browser when you step away or want a second set of eyes.

Free core · Open VSX for Cursor, Windsurf, Trae, and similar editors · No account required

ACP Pro running parallel AI coding-agent sessions with visible tasks and controls
release
0.3.2

Current public build

agents
Any ACP

Registry + defaults

sessions
Parallel

Isolated context per tab

Agent compatibility

Built-ins, ready to launch.Now with a dedicated editor-tab settings experience.

Start any built-in agent through its maintained ACP command, or add more compatible agents from the growing ACP Registry.

Browse the ACP Registry
Claude CodeCodexGrok BuildOpenCodeGitHub CopilotQwen CodeAuggie CLIQoder CLIOpenClawMore agents

How it works

From agent setup to work that follows you.Inspectable in the IDE. Reachable in a browser.

Choose the right agents, keep every step inspectable, and open the same live workspace in a browser when you move away from VS Code.

Follow live execution
ACP Pro sidebar showing parallel sessions, a live file diff, completed tool calls, git context, and composer controls
Plans and controls
ACP Pro task plan, token and cost usage, model toolbar, permission control, and message composer

Keep the whole run in view.Evidence before you accept the result.

Plans, streamed tool calls, file diffs, git context, token and cost usage, model controls, and permission mode stay visible around the conversation.

Why it helps

Review the evidence, cost, and completion state before accepting an agent’s result.

Browse the registry
ACP Pro agent registry open in VS Code with compatible coding agents ready to add
Configure your lineup
ACP Pro agent settings with editable transport, command, arguments, and environment controls

Build the agent lineup that fits the task.Registry in, editor-tab settings tuned, ready to run.

Browse the ACP Registry, add compatible agents, then manage agents, appearance, license, and extension details from one reusable VS Code editor tab.

Why it helps

Keep specialized agents ready without hard-coding the workspace to one provider.

Desktop browser
ACP Pro live workspace open in a desktop browser with agent tabs, tool results, and a file diff
Phone browser
ACP Pro live workspace on a phone browser showing agent progress, diffs, usage, controls, and the composer

Take the live workspace with you.Same session. Phone or desktop browser.

Open the same workspace in a desktop or phone browser. Check a long-running task after you step away, intervene when needed, or invite a teammate to review the live evidence.

Why it helps

Agent work stays observable beyond your desk—without moving the session out of VS Code.

Built for daily work

Depth where the workflow needs it.Choice, evidence, state, and recovery.

The screenshots show the flow. Underneath it, ACP Pro keeps agent choice, execution evidence, codebase state, and recovery organized for repeated use.

Session workspace

Move between active and recent work without losing each tab’s setup.

One switcher for every session

Search Live and Recent conversations, close live sessions, and restore their history later.

Per-tab cwd and fork

Choose a working directory from the header, then fork a tab with the same agent, model, mode, and cwd.

Bounded live processes

Cap live agents and dehydrate finished idle sessions while active work, drafts, prompts, and remote views stay live.

Visible execution

Follow the plan, inspect the evidence, and keep results readable.

Plans stay readable

Track execution in a task panel while reasoning stays in a separate expandable block.

Tool work you can inspect

Follow tool calls as they stream, with clear status, changed-line totals, and inline diffs.

Interactive diagrams and rich answers

Completed Mermaid fences become responsive diagrams with pan, zoom, source copy, and SVG export; unfinished or invalid source stays readable.

Continuity and control

Keep prompts, agent controls, and long transcripts steady as work evolves.

Attachments that come back

Add files and selections, queue follow-ups, or schedule a draft; attachment previews resolve across clients and restored sessions.

Settings in an editor tab

Open one reusable VS Code tab for agents, appearance, license, and About information sourced from extension metadata.

Restored transcripts stay settled

Long transcripts keep each tab’s reading position and bottom-follow intent, and the first new prompt stays pinned after history loads.

License

Free to use.Pro adds control for browser access.

Every core agent workflow stays free. A Pro activation follows your VS Code client profile across local and remote workspaces while protected host keys keep the browser-access entitlement bound to approved environments.

Get a Pro license

What Pro adds

  • Core ACP chat experience remains free
  • Persistent custom browser access code
  • Owner password for browser control
  • Read-only/full-write browser toggle
  • One activation across a VS Code client profile
  • Offline-resilient validated license state

FAQ

Short answers before you install.Requirements, providers, license, and remote access.

Which VS Code version is required?

ACP Pro requires VS Code 1.96 or later and Node.js 20 or later for agents launched through npx.

Does ACP Pro only work with one provider?

No. ACP Pro speaks Agent Client Protocol, so it can work with Claude Code, Codex CLI, Copilot CLI, Gemini CLI, Qwen Code, OpenCode, and any compatible agent.

Is the extension free?

The core extension is free to install and use. A Pro license unlocks optional browser-access controls such as a persistent access code and owner password.

Can remote browser access be disabled?

Yes. Browser access can be turned off per workspace from the Bridge Server settings.