{"version":"2.1.273","anchor":"headlesssdk-session-init-now-threads-a-handoff-relay-marker","canonical_anchor":"headlesssdk-session-init-now-threads-a-handoff-relay-marker","heading":"Headless\/SDK session init now threads a handoff relay marker","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/headlesssdk-session-init-now-threads-a-handoff-relay-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Headless\/SDK session init now threads a handoff relay marker\n\nHeadless and SDK session setup now carries an internal handoff relay marker\n\n**Unclear.** What `handoffRelay` is used for, or what user-facing effect it has, isn't established by the evidence.\n\n**What**\n\nWhen Claude Code starts a headless session (used by the SDK or CLI harness), the internal options object built for it \u2014 which already includes things like `thinkingConfig`, `jsonSchema`, `initialMessages`, and `agents` \u2014 now also includes a `handoffRelay` field. It's only set when both an internal value and a matching internal flag are present; otherwise it's left unset.\n\n**Why**\n\nThe finding doesn't say what consumes `handoffRelay` or what user-visible behavior it enables, so it's not clear yet what this changes in practice.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}