{"version":"2.1.292","anchor":"background-consent-gate-log-wording-and-handoff-history-memo","canonical_anchor":"background-consent-gate-log-wording-and-handoff-history-memo","heading":"Stricter checks on handoff requests, and memory restored in more cases","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/background-consent-gate-log-wording-and-handoff-history-memo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Stricter checks on handoff requests, and memory restored in more cases\n\nA handoff that asks Claude Code to run calls must now start with a non-empty user message, and memory snapshots are applied in more history requests\n\n**What**\n\nThree changes affect sessions started or handed over in the background:\n\n- A handoff request that names calls to run is now refused with `invalid_handoff` unless its first message is a user message that is not empty and is not a tool result.\n\n- The cowork memory snapshot is now also applied on a history request that has no calls and is not stopped, when the session holds none of that request's messages.\n\n- The log line for the background startup check now calls it \"bg consent gate\" instead of \"bg Fable gate\".\n\n**Why**\n\nBadly formed handoffs are now turned away with a clear reason instead of being run, and the session's memory is restored in more situations.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}