{"version":"2.1.280","anchor":"peer-handback-queued-command-replay-logic-added","canonical_anchor":"peer-handback-queued-command-replay-logic-added","heading":"Peer handback queued-command replay logic added","tier":"internal","area":"Multi-Machine","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/peer-handback-queued-command-replay-logic-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Peer handback queued-command replay logic added\n\nClaude Code can now replay queued commands handed back from a peer session\n\n**Unclear.** The finding does not say what triggers a peer handback or how the replayed commands are used once collected.\n\n**What**\n\nA new internal function scans the messages that come after the most recent assistant reply and looks for queued commands that were attached as part of a \"peer handback\" (marked with `origin.kind === 'peer'` and `origin.handback === true`). Commands matching this pattern that haven't already been processed are collected so they can be replayed or restored.\n\nThis appears to relate to handing off work between linked sessions, where one session passes queued commands to another (a \"peer\") and those commands need to be picked back up.\n\n**Why**\n\nThis should help make sure commands queued during a handoff between sessions aren't lost or dropped, restoring them so they still get executed after the handback.\n\n- Area: Multi-Machine\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}