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.

Sources: [1] JetBrains

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.

Sources: [1] JetBrains
FieldCurrent evidence
Primary sourceJetBrains: ACP Agent Registry Is Live: Find and Connect AI Coding Agents in Your JetBrains IDE
Source date2026-01-28
Update scopeAgent Client Protocol, IDE agent discovery, one-click installation, and multi-agent choice
Verification noteOfficial source only; no search-result scraping, no ranking guarantee, no uncited claims
Sources: [1] JetBrains

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.

Sources: [1] JetBrains

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.

Sources: [1] JetBrains

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.

Sources: [1] JetBrains

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.

Sources: [1] JetBrains

Questions This Update Answers

What changed in this update?

JetBrains and Zed launched an ACP Agent Registry so developers can discover and install compatible AI coding agents directly inside supported IDEs.

Why does this matter for agent workflow teams?

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.

What sources support this article?

The article is based on source records from JetBrains, with links and publication dates listed in the Sources section.