{"version":"2.1.236","anchor":"paths-and-titles-are-sanitised-before-they-are-shown","canonical_anchor":"paths-and-titles-are-sanitised-before-they-are-shown","heading":"Paths and titles are sanitised before they are shown","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/paths-and-titles-are-sanitised-before-they-are-shown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Paths and titles are sanitised before they are shown\n\nOdd or hostile paths and links now display as safe placeholders instead of raw characters.\n\n**What**\n\nPaths, titles and urls in artifact permission prompts, tool headers and result lines are run through printability and homoglyph checks with a length cap, so hostile or unprintable input shows as `(unprintable path)` or `(unrecognized address)` rather than raw bytes.\n\n**Details**\n\n- Arrow and lookalike characters are substituted rather than rendered as-is.\n- Renaming normalises the submitted title (Unicode NFC, emoji tag sequences, control characters stripped) before it is stored.\n\n**Evidence**\n\n`(unprintable path)`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}