Skip to content

Commit ca29b6a

Browse files
benbrandtbenbrandt
authored
docs: Split announcements for RFD updates (#904)
1 parent ba4f267 commit ca29b6a

10 files changed

Lines changed: 327 additions & 204 deletions

‎docs/announcements/acp-agent-registry-stabilized.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: ACP Registry is stabilized
3+
sidebarTitle: ACP Registry stabilized
4+
description: Announcement that the ACP Registry RFD has been completed and the registry is stabilized.
5+
---
6+
7+
**Published:** March 9, 2026
8+
9+
The ACP Registry RFD has moved to Completed and the initial version of the registry is stabilized.
10+
11+
The registry gives ACP clients a standard way to discover, install, and configure compatible agents. It introduces a curated catalog and a shared manifest format so editors and other clients do not need to invent their own integration metadata.
12+
13+
If you want to explore the shipped experience, start with [ACP Registry](/get-started/registry). For the design history and rationale, see the [ACP Agent Registry RFD](/rfds/acp-agent-registry).

‎docs/announcements/implementation-information.mdx‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Implementation information for agents and clients
3+
sidebarTitle: Implementation information
4+
description: Protocol update introducing optional implementation metadata during initialization.
5+
---
6+
7+
**Published:** October 24, 2025
8+
9+
ACP now allows agents and clients to provide information about themselves to the other party during initialization.
10+
11+
The [InitializeRequest](/protocol/schema#initializerequest) message now includes an optional clientInfo field, and the [InitializeResponse](/protocol/schema#initializeresponse) message includes an optional agentInfo field.
12+
13+
This information can be used by clients to show users which agent is running and what version, by both sides to track usage metrics for which agents and clients are most popular among their users, and to help track down issues tied to particular implementation versions.
14+
15+
This follows the existing pattern laid out in the [Model Context Protocol](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#initialization).
16+
17+
This is being introduced as an optional field for now for backwards compatibility. It is possible it will be made required in a future version of the protocol, like MCP, so that both sides can count on this information being available.
18+
19+
For the user-facing protocol guide, see [Implementation Information](/protocol/initialization#implementation-information).

‎docs/announcements/sergey-ignatov-lead-maintainer.mdx‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Sergey Ignatov joins ACP as Lead Maintainer
3+
sidebarTitle: Lead maintainer update
4+
description: Governance announcement about Sergey Ignatov joining ACP as a Lead Maintainer.
5+
---
6+
7+
**Published:** February 18, 2026
8+
9+
It is with great pleasure that I announce that Sergey Ignatov, from JetBrains, will be joining me as a Lead Maintainer for ACP. Agus Zubiaga will remain a key part of the leadership group as a Core Maintainer.
10+
11+
This is in recognition of Sergey’s many contributions to the protocol. We would not be where we are today without his efforts. In the past few months, Zed and JetBrains have been able to collaborate closely on the protocol, and it is time to reflect that fact more formally in our governance structure.
12+
13+
I have enjoyed the chance to work with Sergey and the entire JetBrains team. There is still much work to be done, but with all of the agent and client teams working together, I am confident we can continue to make the ACP vision a reality: allowing you to collaborate with the agent or agents you love wherever you are already working.
14+
15+
**Ben Brandt**
16+
17+
Zed Industries / ACP Lead Maintainer

‎docs/announcements/session-config-options-stabilized.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Session Config Options are stabilized
3+
sidebarTitle: Config options stabilized
4+
description: Announcement that session-level configuration selectors are now part of the stable ACP protocol.
5+
---
6+
7+
**Published:** February 4, 2026
8+
9+
The Session Config Options RFD has moved to Completed and is stabilized.
10+
11+
Session Config Options give agents a flexible way to expose session-level configuration such as models, modes, reasoning levels, and other selectors. Instead of hard-coding a small set of protocol-level controls, clients can render the options an agent provides and keep them in sync as they change.
12+
13+
The stable protocol documentation is available in [Session Config Options](/protocol/session-config-options), and the design history remains in the [Session Config Options RFD](/rfds/session-config-options).

‎docs/announcements/session-info-update-stabilized.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Session Info Update is stabilized
3+
sidebarTitle: Session Info Update stabilized
4+
description: Announcement that the session_info_update notification is now part of the stable ACP protocol.
5+
---
6+
7+
**Published:** March 9, 2026
8+
9+
The Session Info Update RFD has moved to Completed and the session_info_update notification is stabilized.
10+
11+
This lets agents push session metadata updates to clients in real time, including generated titles and related metadata, so session lists can stay current without polling.
12+
13+
The stable protocol behavior is documented in [Session List](/protocol/session-list#updating-session-metadata), and the design history remains in the [Session Info Update RFD](/rfds/session-info-update).

‎docs/announcements/session-list-stabilized.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Session List is stabilized
3+
sidebarTitle: Session List stabilized
4+
description: Announcement that the session/list method is now part of the stable ACP protocol.
5+
---
6+
7+
**Published:** March 9, 2026
8+
9+
The Session List RFD has moved to Completed and the session/list method is stabilized.
10+
11+
This gives clients a standard way to discover sessions known to an agent, making features like session history, session switching, and cleanup much easier to implement consistently across ACP clients.
12+
13+
For the shipped protocol, see [Session List](/protocol/session-list). For the design history, see the [Session List RFD](/rfds/session-list).

‎docs/docs.json‎

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,7 @@
108108
"tab": "RFDs",
109109
"pages": [
110110
"rfds/about",
111+
"rfds/updates",
111112
{
112113
"group": "Draft",
113114
"pages": [
@@ -165,7 +166,20 @@
165166
},
166167
{
167168
"tab": "Updates",
168-
"pages": ["updates"]
169+
"pages": [
170+
"updates",
171+
{
172+
"group": "Announcements",
173+
"pages": [
174+
"announcements/acp-agent-registry-stabilized",
175+
"announcements/session-info-update-stabilized",
176+
"announcements/session-list-stabilized",
177+
"announcements/sergey-ignatov-lead-maintainer",
178+
"announcements/session-config-options-stabilized",
179+
"announcements/implementation-information"
180+
]
181+
}
182+
]
169183
},
170184
{
171185
"tab": "Brand",

‎docs/rfds/about.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Some changes do not require an RFD:
2626

2727
RFD proposals are merged into the "Draft" section if a core team member decides to champion them. The champion becomes the point-of-contact and will work with authors to make it reality. Once in draft, implementation may begin (properly feature-gated with the RFD name). Implementation can also begin at a particular SDK or agent/client level to prove out the design for better review and feedback before broader adoption.
2828

29-
RFDs are living documents that track implementation progress. PRs working towards an RFC will typically update it to reflect changes in design or direction.
29+
RFDs are living documents that track implementation progress. PRs working towards an RFD will typically update it to reflect changes in design or direction.
3030

3131
### 2b. Move to "To be removed"
3232

‎docs/rfds/updates.mdx‎

Lines changed: 194 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,194 @@
1+
---
2+
title: RFD Updates
3+
description: Lifecycle updates for ACP Requests for Dialog
4+
rss: true
5+
---
6+
7+
This page tracks lifecycle changes for ACP Requests for Dialog. For broader ACP announcements, see [Updates](/updates).
8+
9+
<Update label="March 27, 2026" tags={["Draft"]}>
10+
## Custom LLM Endpoint RFD moves to Draft stage
11+
12+
The RFD for allowing clients to specify custom provider configuration has been moved to Draft stage. Please review the [RFD](/rfds/custom-llm-endpoint) for more information on the current proposal and provide feedback as work on the implementation begins.
13+
14+
</Update>
15+
16+
<Update label="March 24, 2026" tags={["Draft"]}>
17+
## Additional Directories RFD moves to Draft stage
18+
19+
The RFD for allowing clients to specify additional directories for the agent to access has been moved to Draft stage. Please review the [RFD](/rfds/additional-directories) for more information on the current proposal and provide feedback as work on the implementation begins.
20+
21+
</Update>
22+
23+
<Update label="March 9, 2026" tags={["Completed"]}>
24+
## ACP Registry RFD moves to Completed
25+
26+
The RFD for the initial version of the ACP Registry has been completed. Please review the [documentation](/get-started/registry) for more information.
27+
28+
## session_info_update Notification RFD moves to Completed
29+
30+
The RFD for the session_info_update notification has been stabilized and is now a part of the protocol. Please review the [documentation](/protocol/session-list#updating-session-metadata) for more information.
31+
32+
## session/list RFD moves to Completed
33+
34+
The RFD for the session/list method has been stabilized and is now a part of the protocol. Please review the [documentation](/protocol/session-list) for more information.
35+
36+
</Update>
37+
38+
<Update label="February 24, 2026" tags={["Draft"]}>
39+
## Next Edit Suggestions RFD moves to Draft stage
40+
41+
The RFD for allowing agents to provide next edit suggestions has been moved to Draft stage. Please review the [RFD](/rfds/next-edit-suggestions) for more information on the current proposal and provide feedback as work on the implementation begins.
42+
43+
## session/close RFD moves to Draft stage
44+
45+
The RFD for allowing agents to close a given session has been moved to Draft stage. Please review the [RFD](/rfds/session-close) for more information on the current proposal and provide feedback as work on the implementation begins.
46+
47+
## Elicitation RFD moves to Draft stage
48+
49+
The RFD for allowing agents to elicit user input has been moved to Draft stage. Please review the [RFD](/rfds/elicitation) for more information on the current proposal and provide feedback as work on the implementation begins.
50+
51+
## Boolean Config Option RFD moves to Draft stage
52+
53+
The RFD for adding boolean config options to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/boolean-config-option) for more information on the current proposal and provide feedback as work on the implementation begins.
54+
55+
</Update>
56+
57+
<Update label="February 20, 2026" tags={["Draft"]}>
58+
## Delete in Diff RFD moves to Draft stage
59+
60+
The RFD for indicating whether a diff resulted in a file deletion has been moved to Draft stage. Please review the [RFD](/rfds/diff-delete) for more information on the current proposal and provide feedback as work on the implementation begins.
61+
62+
</Update>
63+
64+
<Update label="February 18, 2026" tags={["Draft"]}>
65+
## Message ID RFD moves to Draft stage
66+
67+
The RFD for adding message ids to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/message-id) for more information on the current proposal and provide feedback as work on the implementation begins.
68+
69+
</Update>
70+
71+
<Update label="February 18, 2026" tags={["Preview"]}>
72+
## session/list RFD moves to Preview stage
73+
74+
The RFD for the session/list method has been moved to Preview stage. Please review the [RFD](/rfds/session-list) for more information on the current proposal and provide feedback before the feature is stabilized.
75+
76+
## session_info_update RFD moves to Preview stage
77+
78+
The RFD for the session_info_update notification has been moved to Preview stage. Please review the [RFD](/rfds/session-info-update) for more information on the current proposal and provide feedback before the feature is stabilized.
79+
80+
</Update>
81+
82+
<Update label="February 10, 2026" tags={["Preview"]}>
83+
## ACP Registry RFD moves to Preview stage
84+
85+
The RFD for the ACP Registry has been moved to Preview stage. Please review the [RFD](/rfds/acp-agent-registry) for more information on the current proposal and provide feedback before the feature is stabilized.
86+
87+
</Update>
88+
89+
<Update label="February 4, 2026" tags={["Completed"]}>
90+
## Session Config Options RFD moves to Completed
91+
92+
The RFD for adding more generic Session Config Options to the protocol has been stabilized and is now a part of the protocol. Please review the [documentation](/protocol/session-config-options) for more information.
93+
94+
</Update>
95+
96+
<Update label="February 4, 2026" tags={["Draft"]}>
97+
## session/delete moves to Draft stage
98+
99+
The RFD for allowing clients to delete a given session has been moved to Draft stage. Please review the [RFD](/rfds/session-delete) for more information on the current proposal and provide feedback as work on the implementation begins.
100+
101+
## Logout method moves to Draft stage
102+
103+
The RFD for allowing clients to logout from an agent connection has been moved to Draft stage. Please review the [RFD](/rfds/logout-method) for more information on the current proposal and provide feedback as work on the implementation begins.
104+
105+
</Update>
106+
107+
<Update label="January 15, 2026" tags={["Draft"]}>
108+
## Rust SDK based on SACP RFD moves to Draft stage
109+
110+
The RFD for basing the Rust SDK on SACP has been moved to Draft stage. Please review the [RFD](/rfds/rust-sdk-v1) for more information on the current proposal and provide feedback as work on the implementation begins.
111+
112+
</Update>
113+
114+
<Update label="January 15, 2026" tags={["Preview"]}>
115+
## Session Config Options RFD moves to Preview stage
116+
117+
The RFD for adding more generic Session Config Options to the protocol has been moved to Preview stage. Please review the [RFD](/rfds/session-config-options) for more information on the current proposal and provide feedback before the feature is stabilized.
118+
119+
</Update>
120+
121+
<Update label="January 14, 2026" tags={["Draft"]}>
122+
## Authentication Methods RFD moves to Draft stage
123+
124+
The RFD for creating additional types of authentication methods has been moved to Draft stage. Please review the [RFD](/rfds/auth-methods) for more information on the current proposal and provide feedback as work on the implementation begins.
125+
126+
</Update>
127+
128+
<Update label="January 1, 2026" tags={["Draft"]}>
129+
## Agent Registry RFD moves to Draft stage
130+
131+
The RFD for creating an Agent Registry has been moved to Draft stage. Please review the [RFD](/rfds/acp-agent-registry) for more information on the current proposal and provide feedback as work on the implementation begins.
132+
133+
## Session Usage RFD moves to Draft stage
134+
135+
The RFD for adding a new usage_update variant on the session/update notification and usage field on prompt responses in the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-usage) for more information on the current proposal and provide feedback as work on the implementation begins.
136+
137+
</Update>
138+
139+
<Update label="December 31, 2025" tags={["Draft"]}>
140+
## Proxy Chains RFD moves to Draft stage
141+
142+
The RFD for adding proxy chain functionality in the protocol has been moved to Draft stage. Please review the [RFD](/rfds/proxy-chains) for more information on the current proposal and provide feedback as work on the implementation begins.
143+
144+
</Update>
145+
146+
<Update label="December 11, 2025" tags={["Draft"]}>
147+
## Agent Telemetry Export RFD moves to Draft stage
148+
149+
The RFD for providing more guidance on how agents should export telemetry has been moved to Draft stage. Please review the [RFD](/rfds/agent-telemetry-export) for more information on the current proposal and provide feedback as work on the implementation begins.
150+
151+
</Update>
152+
153+
<Update label="December 3, 2025" tags={["Draft"]}>
154+
## session_info_update notification RFD moves to Draft stage
155+
156+
The RFD for adding a new session_info_update variant on the session/update notification in the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-info-update) for more information on the current proposal and provide feedback as work on the implementation begins.
157+
158+
## \_meta Propagation RFD moves to Draft stage
159+
160+
The RFD for providing more guidance on how the \_meta parameter should be used within the protocol has been moved to Draft stage. Please review the [RFD](/rfds/meta-propagation) for more information on the current proposal and provide feedback as work on the implementation begins.
161+
162+
</Update>
163+
164+
<Update label="November 26, 2025" tags={["Draft"]}>
165+
## session/resume RFD moves to Draft stage
166+
167+
The RFD for adding a session/resume method to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-resume) for more information on the current proposal and provide feedback as work on the implementation begins.
168+
169+
</Update>
170+
171+
<Update label="November 20, 2025" tags={["Draft"]}>
172+
## $/cancelRequest RFD moves to Draft stage
173+
174+
The RFD for adding a $/cancelRequest method to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/request-cancellation) for more information on the current proposal and provide feedback as work on the implementation begins.
175+
176+
## session/fork RFD moves to Draft stage
177+
178+
The RFD for adding a session/fork method to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-fork) for more information on the current proposal and provide feedback as work on the implementation begins.
179+
180+
</Update>
181+
182+
<Update label="November 3, 2025" tags={["Draft"]}>
183+
## Session Config Options RFD moves to Draft stage
184+
185+
The RFD for adding more generic Session Config Options to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-config-options) for more information on the current proposal and provide feedback as work on the implementation begins.
186+
187+
</Update>
188+
189+
<Update label="October 31, 2025" tags={["Draft"]}>
190+
## session/list RFD moves to Draft stage
191+
192+
The RFD for adding a session/list method to the protocol has been moved to Draft stage. Please review the [RFD](/rfds/session-list) for more information on the current proposal and provide feedback as work on the implementation begins.
193+
194+
</Update>

0 commit comments

Comments
 (0)