Websocket sample needed

[bc3tech]

What would you like to be added?

A sample using websockets as client between client and server.

Proposal(s):

No response

Alternative(s):

No response

Additional info:

I'm struggling to get this A2A lib working w/ websockets. I can get the client connected to the server, but the server isn't successfully responding to requests from a client.

I set up the websockets with endpoint /a2a/{agent} on the server side, then I create the WS Client with endpoint ws://localhost:5173/a2a/MyAgent on the client side. When the request is made, the server returns a 405 (Method not allowed) back to caller.

A sample for websockets would be really helpful!

Community Notes

• Please vote by adding a 👍 reaction to the feature to help us prioritize.
• If you are interested to work on this feature, please leave a comment.

[cdavernas]

@bc3tech Thanks for reporting! It seems it's a bug due to an invalid condition check which should be negated, at

a2a-net/src/a2a-net.Server.AspNetCore/Services/A2AAgentWebSocketMiddleware.cs

Line 37 in 2f7db71

if (context.WebSockets.IsWebSocketRequest)

I opened a new related issue which I'll fix asap. In the meanwhile, please note that I'm thinking of removing the WebSocket transport, as A2A officially only supports the HTTP one. Any thoughts?

[bc3tech]

Ultimately A2A is nothing more than a JSON spec, so what transports you choose to "support" as an SDK is all on you. I, for example, created something long before A2A that works across SignalR (WebSockets), gRPC, WebSockets native, and even MCP. I'm now turning it into an SDK, and built my A2A sample on your pkgs.

We're doing nothing more than throwing JSON across the wire ;)

[cdavernas]

@bc3tech Sure, I theoretically agree with you, and that's why I created the WS transport to begin with, but AFAIK A2A does insist on doing it over HTTP, with SSE streaming.

You can see that being mentionned here:
https://github.com/google/A2A?tab=readme-ov-file#conceptual-overview
And here:
https://google.github.io/A2A/#/documentation?id=transport

[cdavernas]

@bc3tech I love what you are working on, I'll take a deep dive tomorrow.

I think you might be interested in joining the fun in the brand new spec I've been working on: https://github.com/d-clare

[bc3tech]

meh - they can "insist" on whatever they want; they've only really created a JSON schema and naming convention for an endpoint, which is why a WS impl was entirely possible :)

[bc3tech]

@bc3tech I love what you are working on, I'll take a deep dive tomorrow.

I think you might be interested in joining the fun in the brand new spec I've been working on: https://github.com/d-clare

I presented it at Microsoft's recent AI hackathon if you want to watch that: https://aka.ms/yaap-demo
Slides here: https://aka.ms/yaap-slides

[bc3tech]

@bc3tech Sure, I theoretically agree with you, and that's why I created the WS transport to begin with, but AFAIK A2A does insist on doing it over HTTP, with SSE streaming.

You can see that being mentionned here: https://github.com/google/A2A?tab=readme-ov-file#conceptual-overview And here: https://google.github.io/A2A/#/documentation?id=transport

The other thing you have to wonder is how long until they boot SSE just like MCP did and go w/ HTTP Streaming instead.