Under the hood
Useful1 Signal2
Resumed cloud sessions gained a reader that pages events for a single subagent.
What's wrong with this entry?
Anonymous. No account, no email.
What
The cloud client gained a third way to read session events, alongside the whole-session and all-subagents readers: it pages the worker's event feed filtered to one agent id. It is only supplied when the session is a resume, and nothing else is passed otherwise.
Details
- Unlike the other two readers it accepts a cancellation signal, threaded into both the network request and the retry backoff sleep, and bails out immediately if the signal is already aborted.
- Its retry cap is 3 attempts rather than the general 10.
- No feature flag guards it. What causes a single-agent read to be requested lives in the component the reader is handed to, which is not part of this change.
Evidence
session_agent_id
Strings lifted out of the shipped bundle, so the claim above can be checked against them.