{"version":"2.1.314","anchor":"hearth-relay-messages-without-provenance-are-treated-as-invi","canonical_anchor":"hearth-relay-messages-without-provenance-are-treated-as-invi","heading":"Relayed messages with no record of their origin are now kept hidden","tier":"notice","area":"Message Relay","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/hearth-relay-messages-without-provenance-are-treated-as-invi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Relayed messages with no record of their origin are now kept hidden\n\nRelayed messages that have a thread reference but no message IDs or rows are now treated as invisible, not shown as project relay messages\n\n**What**\n\nSome messages reach a session through a relay, for example from a Slack thread or a project. Claude Code now singles out relayed messages that point to a thread but carry no message IDs or message rows, so it has no record of where they came from. These messages are treated as invisible and labelled \"meta-without-provenance\". They used to be handled like any other relayed message. The message queue also no longer skips past them as relayed messages.\n\n**Why**\n\nThis changes how some relayed messages appear and how they are queued. Messages with no traceable origin are now hidden rather than displayed as ordinary relayed messages.\n\n- Area: Message Relay\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}