-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Support for bidirectional communication (prompting the user) #44
Comments
Interesting, I feel like chats are better implemented with websockets - What do you think? @jzanecook |
This might be one of the perfect examples for a plugin referencing #71 since it's something that not all agents might have. |
Can you attend a meeting the Agent protocol meeting on the 12th to discuss this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The protocol currently supports making requests to an agent service. However, some agents may need to be able to communicate with the user in order to function optimally. For example:
Adding a way for agents to prompt the user would greatly increase the versatility of the protocol imo.
Proposal
Two primary options:
Extension of the protocol with a status
awaiting_input
, and a way to resolve this status with additional input for an existing task or stepExtension of the
task
endpoint with acallback
(or similar) attribute through which a client can specify a callback URL which may be polled with prompts for the user until they are resolved.Example:
Responses:
Alternatives
GET /agent/tasks/<task_id>/chats
List chats regarding task
<task_id>
POST /agent/tasks/<task_id>/chats
Start a new chat regarding task
<task_id>
POST /agent/tasks/<task_id>/chats/<chat_id>/messages
Post a new message in an existing chat
GET /agent/tasks/<task_id>/chats/<chat_id>/messages
Get all messages in a chat
POST /agent/tasks/<task_id>/chats/<chat_id>/close
Close/resolve a chat
The text was updated successfully, but these errors were encountered: