{"version":"2.1.282","anchor":"the-unapproved-path-check-now-covers-served-remote-calls","canonical_anchor":"the-unapproved-path-check-now-covers-served-remote-calls","heading":"The check for unapproved paths now has a branch for remote calls","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/the-unapproved-path-check-now-covers-served-remote-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### The check for unapproved paths now has a branch for remote calls\n\nThe check that flags unapproved file paths now has a branch for remote calls, but remote calls still skip it\n\n**Unclear.** It is not clear whether the new branch for remote calls can run at all.\n\n**What**\n\nClaude Code has a check that marks a file path as \"unapproved\". It used to skip remote calls entirely. It now has a branch that would flag the first matching path of a remote call as unapproved. However, another check still switches this off for every remote call, so remote calls still skip the check as before.\n\n**Why**\n\nFor now this is unlikely to change anything you see.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}