You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: Make first section be "Get Started" and move the registry content there (#421)
* Restructure first section of docs and adjust content
* Run pnpm format
* Update script with new page location
* Run pnpm format again
* nonpermanent redirect
---------
Co-authored-by: Ben Brandt <benjamin.j.brandt@gmail.com>
Copy file name to clipboardExpand all lines: docs/get-started/architecture.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Architecture"
3
-
description: "Overview of the Agent Client Protocol architecture"
3
+
description: "Overview of the Agent Client Protocol architecture."
4
4
---
5
5
6
6
The Agent Client Protocol defines a standard interface for communication between AI agents and client applications. The architecture is designed to be flexible, extensible, and platform-agnostic.
Copy file name to clipboardExpand all lines: docs/get-started/introduction.mdx
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: "Introduction"
3
-
description: "Get started with the Agent Client Protocol (ACP)"
3
+
description: "Get started with the Agent Client Protocol."
4
4
---
5
5
6
-
The Agent Client Protocol standardizes communication between code editors/IDEs and coding agents and is suitable for both local and remote scenarios.
6
+
The Agent Client Protocol (ACP) standardizes communication between code editors/IDEs and coding agents and is suitable for both local and remote scenarios.
7
7
8
8
## Why ACP?
9
9
@@ -28,7 +28,11 @@ ACP is suitable for both local and remote scenarios:
28
28
-**Local agents** run as sub-processes of the code editor, communicating via JSON-RPC over stdio.
29
29
-**Remote agents** can be hosted in the cloud or on separate infrastructure, communicating over HTTP or WebSocket
30
30
31
-
> **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.
31
+
<Info>
32
+
Full support for remote agents is a work in progress. We are actively
33
+
collaborating with agentic platforms to ensure the protocol addresses the
34
+
specific requirements of cloud-hosted and remote deployment scenarios.
35
+
</Info>
32
36
33
37
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.
0 commit comments