{"version":"2.1.247","anchor":"a-single-agent-event-reader-was-added-for-resumed-cloud-sess","canonical_anchor":"a-single-agent-event-reader-was-added-for-resumed-cloud-sess","heading":"A single-agent event reader was added for resumed cloud sessions","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-single-agent-event-reader-was-added-for-resumed-cloud-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A single-agent event reader was added for resumed cloud sessions\n\nResumed cloud sessions gained a reader that pages events for a single subagent.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- 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.\n- Its retry cap is 3 attempts rather than the general 10.\n- 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.\n\n**Evidence**\n\n`session_agent_id`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}