From 94f66cc747d49f249d086790eb4fe678cfea5e71 Mon Sep 17 00:00:00 2001 From: Sergey Ignatov Date: Thu, 25 Dec 2025 15:13:41 +0100 Subject: [PATCH] Expand introduction with details on local and remote agent support --- docs/overview/introduction.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/overview/introduction.mdx b/docs/overview/introduction.mdx index e8f6183..a7e0033 100644 --- a/docs/overview/introduction.mdx +++ b/docs/overview/introduction.mdx @@ -23,6 +23,13 @@ This decoupling allows both sides to innovate independently while giving develop ACP assumes that the user is primarily in their editor, and wants to reach out and use agents to assist them with specific tasks. -Agents run as sub-processes of the code editor, and communicate using JSON-RPC over stdio. The protocol re-uses the JSON representations used in MCP where possible, but includes custom types for useful agentic coding UX elements, like displaying diffs. +ACP is suitable for both local and remote scenarios: + +- **Local agents** run as sub-processes of the code editor, communicating via JSON-RPC over stdio. +- **Remote agents** can be hosted in the cloud or on separate infrastructure, communicating over HTTP or WebSocket + +> **Note:** Full support for remote agents is a work in progress. We are actively collaborating with agentic platforms to ensure the protocol addresses the specific requirements of cloud-hosted and remote deployment scenarios. + +The protocol re-uses the JSON representations used in MCP where possible, but includes custom types for useful agentic coding UX elements, like displaying diffs. The default format for user-readable text is Markdown, which allows enough flexibility to represent rich formatting without requiring that the code editor is capable of rendering HTML.