{"version":"2.1.273","anchor":"agent-intent-forwarding-simplified-new-contextonly-and-r","canonical_anchor":"agent-intent-forwarding-simplified-new-contextonly-and-r","heading":"Agent-resume intent forwarding reworked: live\/snapshot delivery and new safeguards","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/agent-intent-forwarding-simplified-new-contextonly-and-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Agent-resume intent forwarding reworked: live\/snapshot delivery and new safeguards\n\nResuming an agent now forwards owner messages via explicit live\/snapshot modes, with simplified gating and new telemetry for edge cases\n\n**What**\n\n- The internal mechanism that forwards a user's (\"owner's\") queued messages into a resumed agent's conversation was simplified: it no longer checks a feature-enabled config plus an owner check, and instead takes explicit `resumed` and `contextOnly` flags. When `contextOnly` is set, the forwarded turns are relabeled with source `unattributed`.\n\n- Resuming an agent in the background now supports a `liveTranscript` setting that picks between `live` and `snapshot` delivery of forwarded messages; the forwarded content is spliced into the resumed agent's prompt before it continues.\n\n- A new telemetry event fires when an agent is resumed that's flagged as an \"observer\" but its observer status can't be confirmed, while the `CLAUDE_CODE_FORWARD_USER_INTENT` setting is active. The `agent_intent_forward` telemetry event also gained a `resumed` field.\n\n**Why** These changes make it more reliable for messages you send while an agent is running to actually reach that agent when it resumes, distinguishing whether they should appear as a live conversation or a one-time snapshot, and flagging cases where Claude Code can't be sure whether an agent should be treated as an observer.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}