{"version":"2.1.281","anchor":"path-safety-check-refuses-paths-that-cannot-be-fully-resolve","canonical_anchor":"path-safety-check-refuses-paths-that-cannot-be-fully-resolve","heading":"Path safety check refuses paths that cannot be fully resolved","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/path-safety-check-refuses-paths-that-cannot-be-fully-resolve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Path safety check refuses paths that cannot be fully resolved\n\nClaude Code now refuses a file path when it cannot fully resolve shortcuts or ~ in it\n\n**Unclear.** The finding does not say which features rely on this check.\n\n**What**\n\nA path safety check now refuses a path when it cannot be fully resolved. This covers following a symlink (a file that points to another location) and expanding `~` (shorthand for your home folder). Before, only the existing refusal cases applied.\n\n**Why**\n\nA path whose real destination is unclear is refused instead of being used as if it were safe."}