{"version":"2.1.310","anchor":"remote-control-hook-ask-host-rules-narrowed-by-location","canonical_anchor":"remote-control-hook-ask-host-rules-narrowed-by-location","heading":"Remote-control permission questions now use only your deny rules unless run here","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/remote-control-hook-ask-host-rules-narrowed-by-location","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Remote-control permission questions now use only your deny rules unless run here\n\nUnder remote control, Claude Code now applies all your local permission rules only when the request is marked as here; otherwise only your deny rules apply\n\n**Unclear.** What location counts as \"here\" is not spelled out.\n\n**What**\n\nPermission rules are settings that allow an action, ask you first, or deny it. When Claude Code handles a permission question under remote control, it decides how many of your local rules to apply. Before, it applied either all of them or none.\n\nThere are now three outcomes:\n\n- none of your rules, when local rules are not honoured\n\n- all of your rules, when local rules are honoured and the request's location is \"here\"\n\n- only your deny rules, when local rules are honoured and the location is anywhere else\n\n**Why**\n\nYour allow rules may no longer approve an action that runs somewhere else, while your deny rules still block it. If something you expect to be allowed starts asking for approval under remote control, this is a likely reason.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}