{"version":"2.1.221","anchor":"terminal-escape-sequence-scanning-handles-can-and-sub-termin","canonical_anchor":"terminal-escape-sequence-scanning-handles-can-and-sub-termin","heading":"Terminal escape-sequence scanning handles CAN and SUB terminators","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/terminal-escape-sequence-scanning-handles-can-and-sub-termin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Terminal escape-sequence scanning handles CAN and SUB terminators\n\nFixes garbled background session output when terminal escape sequences end oddly or split across reads.\n\n**What**\n\nThe string-terminator scan in the background-session output parser was rewritten to walk bytes rather than search for a fixed terminator substring.\n\n**Details**\n\n- looks for ESC, CAN (24) or SUB (26); CAN and SUB now end the sequence\n- handles ESC-backslash\n- carries a pending-ESC state across chunk boundaries so a sequence split between reads is still recognised\n\n**Evidence**\n\n`interactive-mark`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}