Remote Agent
Transport Behavior
Understand the HTTP transport, response formats, and event delivery behavior used by RemoteAgent
Transport Behavior
RemoteAgent currently calls the server through HTTP SDK routes.
Regular requests
For example:
- create session
- list sessions
prompthistoryfork
Those use normal JSON request-response exchanges.
Event subscription requests
events uses an NDJSON-style long-lived response.
That means the client receives JSON events one line at a time.
Each line can be treated as an independent session event.
What this means for callers
- if you only care about one turn result, wait for
turn.finished - if you are building a real-time UI, use
subscribe()
If you want to show tool activity, progressive output, or real-time chat UI, subscribe() is usually the right fit.