JetBrains has announced it will co-develop the Agent Client Protocol with us. They plan to bring ACP support to their entire IDE lineup – IntelliJ IDEA, PyCharm, WebStorm, and the rest of their ecosystem – giving developers the freedom to use any ACP-compatible agent in the tools they already know and love.
JetBrains reached out to us when we launched ACP. They’d been exploring how to standardize agent support across their IDEs – for their own agent, Junie, and others like Codex and Gemini CLI. After meeting with us, they decided ACP was the right approach and we’re excited to have them on board.
This is a major milestone for ACP and for developer choice, and we’re eager to work with them on evolving t…
JetBrains has announced it will co-develop the Agent Client Protocol with us. They plan to bring ACP support to their entire IDE lineup – IntelliJ IDEA, PyCharm, WebStorm, and the rest of their ecosystem – giving developers the freedom to use any ACP-compatible agent in the tools they already know and love.
JetBrains reached out to us when we launched ACP. They’d been exploring how to standardize agent support across their IDEs – for their own agent, Junie, and others like Codex and Gemini CLI. After meeting with us, they decided ACP was the right approach and we’re excited to have them on board.
This is a major milestone for ACP and for developer choice, and we’re eager to work with them on evolving the protocol. Together, we’re focused on getting more agents and clients to follow suit.
Real Momentum
When we launched ACP a few months ago with Google and Gemini CLI, our goal was simple: create an open standard so any agent could work with any editor. Since then, we’ve seen steady adoption from the community.
JetBrains changes the equation. They’re going beyond adoption to actively shape the future of ACP with us. With JetBrains committed, ACP is becoming a real standard for agents to work with UI.
Implementing ACP is a no-brainer for agents. One protocol implementation gets you in front of Zed, Neovim, Emacs, and millions of JetBrains users. Now is the time to get on board.
Why ACP
ACP separates agents from editors. Agents implement one protocol and work everywhere. Editors adopt one protocol and support every agent.
For agent developers, this means focusing on what matters: your agent’s intelligence and capabilities. No custom integrations to maintain for each editor. No one-off deals with every IDE. Implement ACP once and your agent runs wherever developers work.
For users, it means no vendor lock-in. No compromises. Just your preferred agent(s) in your favorite UI(s).
The Time to Build is Now
We’re serious about making ACP the standard for agent-editor integration. We want every agent working in every compatible editor. And JetBrains is proof that this vision is becoming reality.
If you’ve been building an agent and hesitated about ACP support because the ecosystem seemed too nascent, the time to adopt is now. JetBrains’ commitment means your agent can reach a developer audience in the millions across dozens of languages and IDEs.
If you’re a user of an Agent who hasn’t yet adopted ACP, let them know you want them to. To make it easy for you, we found some places where you can make your opinion heard:
- Codex
- Claude Code
- Opencode
- Augment
- Sourcegraph
- Or open an issue/discussion with your preferred agent And here’s the issue link for all the VS Code users out there.
We’re building ACP to reduce duplicated work, enable smooth interoperability, and give developers real choice in their tools. If that resonates with you, we’d love to have you involved. Let’s make ACP the standard together.
Looking for a better editor?
You can try Zed today on macOS or Linux. Download now!
We are hiring!
If you’re passionate about the topics we cover on our blog, please consider joining our team to help us ship the future of software development.