ACP Registry RFD moves to Completed
The RFD for the initial version of the ACP Registry has been completed. Please review the documentation for more information.session_info_update Notification RFD moves to Completed
The RFD for the session_info_update notification has been stabilized and is now a part of the protocol. Please review the documentation for more information.session/list RFD moves to Completed
The RFD for the session/list method has been stabilized and is now a part of the protocol. Please review the documentation for more information.Sergey Ignatov is now a Lead Maintainer
It is with great pleasure that I announce that Sergey Ignatov, from JetBrains, will be joining me as a Lead Maintainer role for ACP. Agus Zubiaga will remain a key part of the leadership group as a Core Maintainer.This is in recognition for 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.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(s) you love wherever you are already working.Ben Brandt / Zed Industries / ACP Lead MaintainerSession Config Options RFD moves to Completed
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 for more information.Session Usage RFD moves to Draft stage
The RFD for adding a newusage_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 for more information on the current proposal and provide feedback as work on the implementation begins.session_info_update notification RFD moves to Draft stage
The RFD for adding a newsession_info_update variant on the session/update notification in the protocol has been moved to Draft stage. Please review the RFD for more information on the current proposal and provide feedback as work on the implementation begins.Implementation Information for Agents and Clients
Agents and Clients are now able to provide information about themselves to the other party. TheInitializeRequest message now includes an optional clientInfo field and the InitializeResponse message includes an optional agentInfo field.This information can be used by Clients to show users which Agent is running and what version, by both sides to track usage metrics of which agents and clients are most popular among their users, and also to help track down if any issues are encountered with particular implementation version. This follows the existing pattern laid out in the Model Context Protocol.This is being introduced as an optional field for now for backwards compatibility. It is possible it will be made into a required field in a future version of the protocol, like MCP, so that both sides can count on this information being available.