Menu
Language
Theme
interface AgentServerAdapterPublic v1 name for TransportAdapter plus optional high-level
capabilities. Renamed to reflect that this interface now denotes the
full agent-server protocol contract (not merely wire transport):
any object that satisfies it can back a useStream call. See
plan-custom-transport.md §4 for the rollout.
The extra optional methods let adapters surface thread state and
history without the framework needing to issue a parallel HTTP
request — useStream.hydrate() calls getState?() when present
and falls back to client.threads.getState otherwise. Adapters
that don't know how to produce these values can simply omit them.
The legacy TransportAdapter export is retained for back-compat and
resolves to the same structural type; new code should prefer
AgentServerAdapter.
Thread ID this transport is bound to.
Shuts down the transport and releases any underlying resources.
Streams incoming protocol messages from the remote peer. Used by WebSocket transports where all events share one connection.
Get all past states for a thread.
Get state for a thread.
Opens the underlying connection (e.g. WebSocket handshake). For HTTP/SSE transports this is a no-op.
Opens an independent filtered SSE event stream.
Each call creates a new server connection with the given filter.
Returns undefined when the transport does not support per-subscription
streams (e.g. WebSocket), in which case the caller should fall back to
command-based subscriptions over events.
Replay contract. Implementations MUST buffer events emitted for
the thread/run and replay them through every newly-opened stream
whose filter matches. The SDK's shared-stream rotation relies on
this: when a subscription's filter widens the union, the SDK opens
a fresh stream and expects to receive the run's full history from
seq=0 (deduplication is handled client-side via event_id). The
SDK also defers the open until after run.start has committed the
thread server-side to avoid a 404: Thread not found, which means
events emitted during that window MUST be delivered to the late
opener. The protocol v2 server implements this via a bounded
per-run replay buffer; custom adapters should mirror that.
Sends a command and optionally returns an immediate response.