Developer ToolsAI & IDE

ACP Agent Registry and Vibe Coding: How JetBrains Changes the AI Coding Experience

JetBrains and Zed launched the ACP Agent Registry—a directory of AI coding agents you can discover and install directly in your IDE. Here’s how it affects your vibe coding experience and how to use it in practice.

TL;DR

The Agent Client Protocol (ACP) is like LSP for AI agents: one standard, any editor. The registry lets you browse agents (OpenCode, Mistral Vibe, Gemini CLI, Copilot, etc.), click Install, and switch between them without editing config files. That means less friction and more flow—better vibe coding—with concrete examples below.

7 min read

LogNroll Team

Engineering & Product

What is the ACP Agent Registry?

The Agent Client Protocol (ACP) is an open standard that lets any AI coding agent work in any supporting editor—similar to how the Language Server Protocol (LSP) lets any editor support any language. JetBrains and Zed have integrated the official ACP Agent Registry into JetBrains IDEs (2025.3.2+) and Zed, so you can discover agents, install with one click, and switch between them without editing acp.json by hand.

At launch the registry includes agents like Auggie CLI, Factory Droid, Gemini CLI, GitHub Copilot, Mistral Vibe, OpenCode, and Qwen Code. You get more choice, no vendor lock-in, and the ability to try different agents in the IDE you already use.

How It Affects Vibe Coding

Vibe coding is that state where you stay in flow: you think, you prompt, the agent suggests or edits code, and you keep moving without constant context-switching. The registry directly improves that experience in several ways.

  • Less friction to start: No hunting for install scripts or config docs. Open Settings → Tools → AI Assistant → Agents (or “Install From ACP Registry…”), pick an agent, click Install. You’re coding with an AI in minutes.
  • Pick the agent that fits the vibe: Some agents are tuned for speed (e.g. Mistral Vibe), others for deep codebase understanding (e.g. Gemini CLI) or large refactors (Auggie). You choose what matches your task and preference.
  • Switch by task, not by tool: Use one agent for quick edits and another for architectural discussions—all inside the same IDE and AI Chat tool window, without leaving your project.
  • Stay current with one click: Agents in the registry can be updated from the same place, so you spend less time on maintenance and more time in flow.

Bottom line: The registry makes “try this agent” and “switch agent” part of normal workflow instead of a research project. That’s what improves vibe coding: fewer interruptions, more time in the zone.

Usage Examples

Here are concrete ways to use the ACP Agent Registry in your day-to-day coding.

1. Explain an unfamiliar module with OpenCode

Install OpenCode from the registry, open your project, and in the AI Chat ask: “Walk me through this module and how it fits into the rest of the app.” OpenCode can use different LLMs, so you can experiment with the model that gives you the clearest explanations without leaving the IDE.

Best for: onboarding, legacy code, or quick context when jumping into a new area.

2. Fast, lightweight chat with Mistral Vibe

Install Mistral Vibe when you want a snappy, low-latency assistant for short questions, naming ideas, or small refactors. Use it for “vibe” sessions where you want quick back-and-forth without heavy context.

Best for: quick answers, naming, small edits, and keeping momentum.

3. Deep codebase work with Gemini CLI

Use Gemini CLI when you need strong codebase understanding and multimodal support—e.g. “Suggest a refactor for this service and update the call sites” or “What’s the impact of changing this API?”. Good for larger, more analytical tasks.

Best for: refactors, impact analysis, and design discussions.

4. Switch agents by task

Keep two or three agents installed (e.g. Mistral Vibe for speed, OpenCode for open-source flexibility, GitHub Copilot for integration with your existing subscription). In the agent picker, switch to the one that fits the current task—quick fix vs. big refactor vs. documentation—without changing tools.

Best for: matching the agent to the task and your current vibe.

5. Use Copilot via ACP in JetBrains

If your team already uses GitHub Copilot, you can now use it inside JetBrains IDEs through the ACP registry. Install it from the registry, authenticate, and get the same Copilot experience in the AI Chat tool window—no need to leave your favorite IDE.

Best for: teams standardizing on Copilot who prefer JetBrains.

How to Get Started

In any JetBrains IDE (2025.3.2+) with JetBrains AI (253.30387.147+):

  1. Open Settings → Tools → AI Assistant → Agents, or choose “Install From ACP Registry…” in the agent picker menu.
  2. Browse the list, pick an agent (e.g. OpenCode or Mistral Vibe), and click Install.
  3. Complete any auth the agent needs (Agent Auth or Terminal Auth as required).
  4. Use the agent in the AI Chat tool window. Switch agents from the picker whenever you want.

Agents typically have their own subscription or usage terms; you don’t need a JetBrains AI subscription to use ACP agents. For manual setups or agents not yet in the registry, you can still edit acp.json directly.

Conclusion

The ACP Agent Registry turns “which agent and how do I install it?” into a few clicks. For vibe coding, that means less friction, more choice, and the ability to match the agent to the task without leaving your IDE. Try installing OpenCode or Mistral Vibe from the registry and use the examples above—then switch agents when the task changes and see how it affects your flow.

Learn more

Read the official announcement and try the registry in your IDE.

ACP Agent Registry Is Live (JetBrains AI Blog)

More on the blog