II.
AgentHostTransport JSON
Structured · liveagent-host-transport:grpc
grpc json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "agent-host-transport:grpc",
"_kind": "AgentHostTransport",
"_file": "compute/agent-host-transports/grpc.yaml",
"_cluster": "compute",
"attributes": {
"displayName": "grpc",
"kind": "grpc",
"description": "gRPC bidirectional streaming between agent host and agent process —\nHTTP/2 framed, protobuf-encoded. Used by hosted-agent backends and\nmux gateways that need fan-in/fan-out across many concurrent\ninvocations with backpressure. Distinct from `http` (REST/SSE) and\n`ws` (WebSocket framing).\n",
"inboundMessageFormat": "Protobuf-encoded request messages over a bidirectional streaming RPC.\nMethod definition is per-host — most a5c gateways use a single\n`RunAgent(stream Request) returns (stream Event)` shape.\n",
"outboundMessageFormat": "Protobuf-encoded event messages — turn deltas, tool calls, lifecycle\nevents. Stream-end carries the terminal status.\n",
"signalForwarding": "gRPC cancellation propagates through context cancellation; client-side\n`Context.cancel()` triggers server-side `Context.Done()`. There is no\ndirect POSIX-signal mapping — hosts that need stronger guarantees\nlayer a separate control-plane RPC (e.g. `Cancel(invocationId)`).\n",
"ptySemantics": "None — gRPC is a structured RPC transport, not a terminal substrate.\n"
},
"outgoingEdges": [
{
"from": "agent-host-transport:grpc",
"to": "agent-version:agent-mux-remote@current",
"kind": "used_by"
}
],
"incomingEdges": []
}