Agent Client Protocol (ACP)
|
Implementing https://agentclientprotocol.com/protocol/agent-plan I notice that there are no "entry id" that I could specify. I wonder if the rational is that the content itself suppose to be unique, and we should duplicate based on that. Why wouldn't the spec allow an |
Replies: 1 comment 2 replies
|
Its not required because the protocol requires you to always update ALL entries. there are no operations which require referencing single pan entries. "The Agent MUST send a complete list of all plan entries in each update and their current status. The Client MUST replace the current plan completely." |
|
Oooh I see I see, from the perspective of the "clients" they do not anything complex, just display the list |
|
Yep this is exactly right! We keep it simple since it seems most agents are just recreating the whole plan each time anyway, so you can just render whatever you get statelessly on the clinet |
Its not required because the protocol requires you to always update ALL entries. there are no operations which require referencing single pan entries.
"The Agent MUST send a complete list of all plan entries in each update and their current status. The Client MUST replace the current plan completely."