{"version":"2.1.224","anchor":"host-credentials-path-normalised-like-every-other-sandbox-ru","canonical_anchor":"host-credentials-path-normalised-like-every-other-sandbox-ru","heading":"Host credentials path normalised like every other sandbox rule","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/host-credentials-path-normalised-like-every-other-sandbox-ru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Host credentials path normalised like every other sandbox rule\n\nA trailing slash in your host credentials file path no longer changes whether the rule matches.\n\n**What**\n\nThe file named by `CLAUDE_CODE_HOST_CREDS_FILE` is now run through the same path normaliser as sandbox allow\/deny entries and permission deny rules, so a trailing slash no longer changes whether the rule matches.\n\n**Details**\n\n- Sandbox deny and allow filesystem entries, permission deny rules and the host credentials path all share one trailing-separator-aware normaliser when sandbox rules are built.\n- Previously each of these handled paths its own way.\n\n**Evidence**\n\n`CLAUDE_CODE_HOST_CREDS_FILE`\n\n- Area: Sandbox\n- Names: `CLAUDE_CODE_HOST_CREDS_FILE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}