Expand introduction with details on local and remote agent support

Author: ignatov

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.