{"version":"2.1.271","anchor":"cross-session-hold-receipts-now-surface-in-the-transcript-in","canonical_anchor":"cross-session-hold-receipts-now-surface-in-the-transcript-in","heading":"Cross-session hold receipts now surface in the transcript instead of just logging","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/cross-session-hold-receipts-now-surface-in-the-transcript-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Cross-session hold receipts now surface in the transcript instead of just logging\n\nCross-session hold\/drop\/release notices now appear in the transcript itself, not just in debug logs\n\n**What**\n\nClaude Code can run multiple sessions that talk to each other, and sometimes a message from one session to another has to be held, dropped, or released (parked) rather than delivered right away. Previously, this only produced a debug log line. Now it's tracked more fully:\n\n- Hold\/drop\/release notices are written directly into the session's own transcript as a visible system message, marked as informational with a `warning` level, in addition to still being logged.\n\n- Message state changes (held, dropped, released) are tracked in a lookup table.\n\n- On startup, any messages that were already being held from before get their state seeded correctly.\n\n**Why**\n\nThis means a user can actually see in their conversation when a cross-session message was held up or dropped, instead of that information only existing in hidden debug logs.\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}