{"version":"2.1.287","anchor":"event-delivery-json-mode-nonce-closing-tag","canonical_anchor":"event-delivery-json-mode-nonce-closing-tag","heading":"A second closing form is accepted for delivered event messages","tier":"internal","area":"Channels","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/event-delivery-json-mode-nonce-closing-tag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### A second closing form is accepted for delivered event messages\n\nEvent messages delivered to a session can now end with a second, JSON-mode closing tag that Claude Code accepts and checks\n\n**Unclear.** What switches event delivery into the JSON mode is not shown.\n\n**What**\n\nEvent messages that Claude Code passes into a session can now end with a second form of closing marker, used in a JSON mode, alongside the existing one. Claude Code accepts and checks both forms.\n\n**Why**\n\nIn practice the wrapping around these delivered events can now take two shapes, and both are handled.\n\n- Area: Channels\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}