{"version":"2.1.288","anchor":"cross-session-held-and-expired-delivery-notices-rewritte","canonical_anchor":"cross-session-held-and-expired-delivery-notices-rewritte","heading":"Claude is told clearly when a message to another session was held or expired","tier":"notice","area":"Cross Session","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cross-session-held-and-expired-delivery-notices-rewritte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Claude is told clearly when a message to another session was held or expired\n\nNotices about held or expired messages between sessions now say plainly they were not delivered and explain why\n\n**What**\n\nClaude can send messages to another Claude Code session. When such a message is held, Claude is now told it was NOT delivered, and that it must not report it as delivered or send it again while it is held. The notice explains the usual cause:\n\n- the two sessions use different permission modes, so a terminal session asks its user to approve the message\n\n- the desktop app and non-interactive sessions cannot ask, so the message expires undelivered\n\n- a session can also be set to hold every message\n\nWhen a message expires, Claude is told not to resend it unprompted, since while the modes differ a resend would only be held again.\n\n**Why**\n\nClaude should stop telling you a message reached another session when it did not, and stop resending messages that will only be held again.\n\n- Area: Cross Session\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}