JetBrains ACP Agent Registry Opens IDE Access to Multiple Coding Agents

JetBrains' January 28 post describes the ACP Agent Registry as a directory for AI coding agents inside JetBrains IDEs and Zed. The registry builds on Agent Client Protocol so supporting agents can work across editors through one integration pattern.

The practical value is choice rather than another single-agent surface. Developers can install agents such as Gemini CLI, GitHub Copilot, OpenCode, Qwen Code, or other ACP-compatible tools, then switch based on task, pricing, governance, or team preference.

What This Adds Beyond the Source

The registry is an ecosystem signal more than a single product feature. ACP makes agent interoperability possible; the registry makes it discoverable enough for normal IDE users to try multiple agents without hand-editing configuration first.

Operational Implications

Developer-experience teams should watch ACP because it can reduce lock-in and let teams compare agents inside the IDE they already use. The governance work shifts to deciding which agents are approved, how credentials are handled, and how agent output is reviewed.

Reader Decision Point

This update is useful for teams that want optionality across coding agents. If a company mandates one vendor, the registry may be less urgent, but it still matters as a sign that IDEs are becoming agent marketplaces.

Limits and open questions: the registry is a beta-style ecosystem step, and each agent can still require its own subscription, authentication, and safety model. The article should not imply uniform quality or support across listed agents. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.