{"version":"2.1.310","anchor":"sandbox-denies-on-another-computer-warning-in-status-notices","canonical_anchor":"sandbox-denies-on-another-computer-warning-in-status-notices","heading":"Sandbox warns when deny rules name another computer","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/sandbox-denies-on-another-computer-warning-in-status-notices","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Sandbox warns when deny rules name another computer\n\nClaude Code now warns that sandbox deny paths belonging to another computer are not enforced, with a count and a pointer to \/status\n\n**What**\n\nThe sandbox limits what commands Claude Code runs can reach. Deny rules list paths they may not touch. Claude Code now notices deny entries that belong to another computer.\n\n- A new warning gives a count followed by \"on another computer\" and \"not enforced\", with the hint \"\/status for details\".\n\n- The count comes from a new counter, `sandboxDeniesOnAnotherHostCount`. It starts at 0 and is passed to the status or doctor view.\n\n- New sandbox messages, `deniesOnAnotherHostNotDescribed` and `denyEntryHostNotJudged`, cover cases where Claude Code could not work out whether a deny entry names another computer. One reads \"sandbox: whether a deny entry names another computer could not be worked out\".\n\n**Why**\n\nIf a deny rule names another computer, it does not protect anything on this one. The warning makes that visible, and `\/status` shows the details.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}