II.
AgentHostTransport overview
Reference · liveagent-host-transport:grpc
grpc overview
gRPC bidirectional streaming between agent host and agent process — HTTP/2 framed, protobuf-encoded. Used by hosted-agent backends and adapter gateways that need fan-in/fan-out across many concurrent invocations with backpressure. Distinct from `http` (REST/SSE) and `ws` (WebSocket framing).
Attributes
displayName
grpc
kind
grpc
description
gRPC bidirectional streaming between agent host and agent process —
HTTP/2 framed, protobuf-encoded. Used by hosted-agent backends and
adapter gateways that need fan-in/fan-out across many concurrent
invocations with backpressure. Distinct from `http` (REST/SSE) and
`ws` (WebSocket framing).
inboundMessageFormat
Protobuf-encoded request messages over a bidirectional streaming RPC.
Method definition is per-host — most a5c gateways use a single
`RunAgent(stream Request) returns (stream Event)` shape.
outboundMessageFormat
Protobuf-encoded event messages — turn deltas, tool calls, lifecycle
events. Stream-end carries the terminal status.
signalForwarding
gRPC cancellation propagates through context cancellation; client-side
`Context.cancel()` triggers server-side `Context.Done()`. There is no
direct POSIX-signal mapping — hosts that need stronger guarantees
layer a separate control-plane RPC (e.g. `Cancel(invocationId)`).
ptySemantics
None — gRPC is a structured RPC transport, not a terminal substrate.
Outgoing edges
used_by1
- agent-version:adapters-remote@current·AgentVersion
Incoming edges
None.