{"version":"2.1.269","anchor":"path-safety-check-renamedrefactored-for-read-asset-and-read","canonical_anchor":"path-safety-check-renamedrefactored-for-read-asset-and-read","heading":"Path safety check renamed\/refactored for read_asset and read_file save targets","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/path-safety-check-renamedrefactored-for-read-asset-and-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Path safety check renamed\/refactored for read_asset and read_file save targets\n\nPath-safety check behind read_asset\/read_file save-location errors was renamed internally, with no behavior change\n\n**What**\n\nThe internal check that verifies a save destination (`out_dir`) isn't a network path, used by the `read_asset` and `read_file` tools, was renamed internally. The error messages users see, such as being told a save can only go to local directories when `out_dir` names a network path or can't be resolved, stay the same.\n\n**Why**\n\nThis is a behind-the-scenes rename with the same error messages preserved, so it shouldn't change what users experience when saving assets or files.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}