{"version":"2.1.246","anchor":"settings-entries-cannot-smuggle-auto-mode-region-markers","canonical_anchor":"settings-entries-cannot-smuggle-auto-mode-region-markers","heading":"Settings entries cannot smuggle auto-mode region markers","tier":"notice","area":"Prompt Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/settings-entries-cannot-smuggle-auto-mode-region-markers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Settings entries cannot smuggle auto-mode region markers\n\nSettings entries containing auto-mode region markers are refused so they can't pose as classifier structure.\n\n**What**\n\nSettings entries containing `<cc_automode` or `<\/cc_automode` are now refused. Those tags mark off sections of the text auto mode's classifier reads, so an entry containing one could have posed as classifier structure. This joins the existing refusal of invisible and bidirectional characters and of literal `<settings_` tokens.\n\n**Evidence**\n\n`region tag; entries must not contain classifier region markers.`\n\n- Area: Prompt Safety\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}