{"version":"2.1.319","anchor":"inbox-poller-marks-unverified-provenance-messages-on-idle-de","canonical_anchor":"inbox-poller-marks-unverified-provenance-messages-on-idle-de","heading":"Idle message delivery now checks where messages came from","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/inbox-poller-marks-unverified-provenance-messages-on-idle-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Idle message delivery now checks where messages came from\n\nWhen Claude Code delivers waiting messages while idle, it now takes an extra step if any message's origin is not verified\n\n**Unclear.** What the extra step does with a message whose origin is not verified is not known.\n\n**What**\n\nClaude Code can deliver waiting messages to a session while it is idle. A session is one running conversation with Claude Code. It now checks whether each of those messages comes from a verified source. If any does not, Claude Code takes an extra step during delivery. Before, it made no such check.\n\n**Why**\n\nThe check concerns how far messages passed between sessions can be trusted.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}