feat: introduce transport agnostic client #198
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guglielmo-san
approved these changes
Nov 26, 2025
yarolegovich
approved these changes
Nov 27, 2025
ishymko
added a commit
that referenced
this pull request
Nov 28, 2025
# Description Propagate `RequestOptions` down to `Transport`. Re #198, was missing in the original PR - wasn't release yet, so no impact.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As a next step after #169, define a transport agnostic client.
Changes
Main
Clientbuilt around core types, not JSON-RPC wrappers.ClientFactoryto dynamically select transport among available based on agent card and factory level preferences.Misc
A2ATransporttoTransport(this type is not yet exported viaindex.ts).AbortSignaltoTransportand new client for cancellation.sendMessageandsendMessageStreamusing server SDK wired up with real expressjs app and invoked via newly created client.getTaskPushNotificationConfigtypes in transport.TODOs
Re #137, #142
Release-As: 0.3.6