-
Notifications
You must be signed in to change notification settings - Fork 5.8k
implementing different a2a transport #4176
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
implementing different a2a transport #4176
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
lorenzejay
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only thing is more examples with a2a docs with this, but not a blocker for now
Implementing the support to set the A2A transport type when adding the A2A agent url.
Note
Introduces configurable transport selection across A2A delegation.
transport_protocol: Literal['JSONRPC', 'GRPC', 'HTTP+JSON']toA2AConfig(defaultJSONRPC)transport_protocolthroughexecute_a2a_delegation,aexecute_a2a_delegation, and internal_aexecute_a2a_delegation_implsupported_transports=[transport_protocol]in_create_a2a_clientagent_config.transport_protocolin both sync and async pathstransport_protocoloption indocs/en/learn/a2a-agent-delegation.mdxWritten by Cursor Bugbot for commit e4798bf. This will update automatically on new commits. Configure here.