{"version":"2.1.310","anchor":"sandbox-deny-paths-on-another-computer-are-reported-by-claud","canonical_anchor":"sandbox-deny-paths-on-another-computer-are-reported-by-claud","heading":"Claude Code now warns when sandbox deny rules point at another computer","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/sandbox-deny-paths-on-another-computer-are-reported-by-claud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Claude Code now warns when sandbox deny rules point at another computer\n\nSandbox deny paths on another computer are dropped, and Claude Code now warns at startup and lists them in `claude doctor`\n\n**What**\n\nThe sandbox is a protective boundary that limits what commands Claude Code runs can touch. A deny entry is a rule that blocks access to a path. When sandboxing is on and some deny entries point at a path on another computer (a remote host), the sandbox leaves them out. Claude Code now tells you about this in two places:\n\n- At startup, as a warning printed to stderr (the terminal's error output)\n\n- In `claude doctor`, which lists the affected entries\n\nThe warning begins \"Sandbox deny paths on another computer are not enforced, so sandboxed commands are not blocked from them:\". It also says the rules still apply to Claude Code's file tools, the built-in tools it uses to read and edit files.\n\n**Why**\n\nIf you wrote deny rules for paths on another computer, those rules do not stop sandboxed commands from reaching them. You now hear about it instead of assuming you are protected.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}