ACP
Agent Communication Protocol (ACP) is an open protocol designed to standardize communication interfaces between code editors and AI programming agents. The protocol defines standard message formats and invocation specifications for interactions between editor environments and external programming agents, enabling interoperability across different editor and agent implementations to support unified integration for intelligent programming scenarios such as code completion, automated refactoring, and task execution.
Core Facts
The MCP protocol uses JSON-RPC 2.0 as its underlying communication protocol and defines three core primitives: Resources, Tools, and Prompts.
The Language Server Protocol (LSP) decouples language intelligence suggestion logic from the editor, enabling any programming language to implement the protocol once and obtain auto-completion and error detection in all LSP-compatible editors.
ACP (Agent Communication Protocol) was proposed under the leadership of IBM Research and is an open protocol that standardizes the interaction between Agents and clients.
Timeline (last 90 days)
Zed's ACP configuration defaults now apply only to new sessions, and reopening an existing session preserves its original settings (PR #65850).
In March 2026, OpenAI moved payment capability back into each merchant's own app, while stating that ACP still exists as infrastructure connecting users and merchants.
ACP (Agentic Commerce Protocol) was released as open source by OpenAI and Stripe in September 2025.
In September 2025, OpenAI and Stripe jointly proposed the Agentic Commerce Protocol (ACP), defining a standard interface for AI agents to place orders on behalf of users.
ACP defines a set of JSON-RPC-style request/response and notification messages, covering interactions such as session creation, prompt sending, tool call authorization, and file reading and writing.
Whether ACP, as the only protocol currently showing cross-Agent tendencies, will become a unified standard has no definite answer yet.
There is currently no unified industry standard for the protocol approach, each Agent requires a separately written adapter, and the protocols themselves change at a pace almost in sync with Agent iterations.
ACP is a neutral middle layer, with the Agent side implementing the protocol server and the editor side implementing the client; if multiple Agents all follow ACP, the client only needs to maintain one implementation.
ACP is a protocol released by IBM in March 2025 that powers the BeeAI platform. In August 2025, IBM Research and Google announced that ACP would merge with A2A under the Linux Foundation's LF AI & Data.
ACP had only 1 commit in the same 90-day window.
25 more timeline events
All Facts (20)
The MCP protocol uses JSON-RPC 2.0 as its underlying communication protocol and defines three core primitives: Resources, Tools, and Prompts.
80%VerifiedThe Language Server Protocol (LSP) decouples language intelligence suggestion logic from the editor, enabling any programming language to implement the protocol once and obtain auto-completion and error detection in all LSP-compatible editors.
75%VerifiedACP (Agent Communication Protocol) was proposed under the leadership of IBM Research and is an open protocol that standardizes the interaction between Agents and clients.
75%VerifiedThe ACP protocol aims to standardize the communication protocol between code editors and programming agents.
75%VerifiedZed supports the Agent Client Protocol (ACP) and MCP server protocol.
70%UnverifiedACP与MCP解决不同层面的问题：ACP解决编辑器与代理的通信，MCP解决代理与工具/数据源的通信
95%UnverifiedACP支持接入自定义代理，通过创建JSON配置文件指定代理服务器信息和启动命令即可接入
90%UnverifiedACP的核心抽象是'Agent即服务'，每个Agent都有标准化的输入输出接口，可以像微服务一样被组合和替换
85%UnverifiedACP解决的是'N个代理×M个编辑器'的集成矩阵问题，将集成工作量从M×N压缩为M+N
85%UnverifiedACP（Agent Communication Protocol）是由IBM Research主导、Linux基金会托管的开放协议
80%UnverifiedACP支持实时diff预览，代理生成的代码修改以diff视图直接展示在编辑器中
60%UnverifiedACP is essentially a JSON-RPC-based protocol that typically communicates with subprocesses via standard input/output (stdio).
60%UnverifiedIn September 2025, OpenAI and Stripe jointly proposed the Agentic Commerce Protocol (ACP), defining a standard interface for AI agents to place orders on behalf of users.
50%UnverifiedACP defines a set of JSON-RPC-style request/response and notification messages, covering interactions such as session creation, prompt sending, tool call authorization, and file reading and writing.
50%UnverifiedACP is a neutral middle layer, with the Agent side implementing the protocol server and the editor side implementing the client; if multiple Agents all follow ACP, the client only needs to maintain one implementation.
50%UnverifiedThere is currently no unified industry standard for the protocol approach, each Agent requires a separately written adapter, and the protocols themselves change at a pace almost in sync with Agent iterations.
50%UnverifiedAP2 has 3,226 GitHub stars, 19 contributors, 0 commits in 90 days and 3 MCP servers; ACP has 1,571 GitHub stars, 26 contributors, 1 commit in 90 days and 3 MCP servers; x402 has 6,715 GitHub stars, 334 contributors, 278 commits in 90 days and 222 MCP servers.
50%UnverifiedFor AP2 and ACP, the existence of officially published packages on npm/PyPI cannot be confirmed, so development can only be done by hand-writing implementations according to the specification.
50%UnverifiedACP had only 1 commit in the same 90-day window.
50%UnverifiedACP defines a checkout session among agents, merchants and payment processors, and does not involve ongoing budgets at all.
50%