Can ACP be more generic?

[Areo-Joe]

The Agent Client Protocol (ACP) standardizes communication between code editors (interactive programs for viewing and editing source code) and coding agents (programs that use generative AI to autonomously modify code).

Agent Client Protocol, sounds like a generic protocol for any agent client, but the README says it aims to do the coding agent stuff. Is there a chance that we aim for sth more generic?

Or maybe the protocol is already generic enough that we can use this to create sth other than coding agent?

[benbrandt]

@Areo-Joe glad you are interested! We are obviously going full-speed ahead on making sure this works great for coding agents at the moment, but that doesn't mean it can't evolve in the future. We have tried to be as agnostic as we can about how some of these calls are used to allow for maximum flexibility in agent implementations, while still having consistent flows clients can count on.

That being said, it is possible many of the core sessionUpdate notifications are already enough for many chat agents. I'd say, if you are interested, give it a shot and let us know what you are missing if you run into any issues, and we can discuss protocol updates. Or, if it already works, also let us know!
Thanks!

[Areo-Joe]

Thanks for answering. I will try these couple days. I am currently seeking a generic way to build agent applications.