{"version":"2.1.310","anchor":"windows-nankeen-kestrel-gate-now-remembers-it-has-been-on","canonical_anchor":"windows-nankeen-kestrel-gate-now-remembers-it-has-been-on","heading":"Windows strict sandbox: clear refusal messages and a switch that remembers it was on","tier":"use","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/windows-nankeen-kestrel-gate-now-remembers-it-has-been-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Windows strict sandbox: clear refusal messages and a switch that remembers it was on\n\nOn Windows, strict sandbox mode now explains why a command was refused, and the CLAUDE_CODE_NANKEEN_KESTREL switch remembers it was on\n\n**What**\n\nA sandbox is a fenced-off area where commands run with limited access to your computer. On Windows, Claude Code has a strict sandbox mode in which no command may run outside it. Two pieces changed:\n\n- Refusal messages: when strict sandbox mode is on and a command cannot run inside the sandbox, Claude Code now builds a specific message such as 'The command did not run. Strict sandbox mode is on, so no command may run outside the sandbox'. It says what went wrong: the sandbox was switched off, was not set up, failed to start, or an exclusion was not honoured. It also tells Claude not to work around it. For Bash, the shell tool, this also depends on the `CLAUDE_CODE_NANKEEN_KESTREL` environment variable or the `tengu_nifty_ripple` server switch.\n\n- The switch remembers being on: the Windows-only check on the `CLAUDE_CODE_NANKEEN_KESTREL` environment variable or the `tengu_nankeen_kestrel` server switch now records that it has been on once either returns true. Before, it simply returned the current value. The server switch falls back to off.\n\nThe flag server returned `tengu_nankeen_kestrel` as off for this site's account and for an anonymous visitor, but no reading has been taken under this release yet. Nothing has been read about `tengu_nifty_ripple`.\n\n**Why**\n\nWindows users in strict sandbox mode get an explanation of why a command did not run instead of a generic failure, and Claude is told not to try to get around the sandbox. Remembering that the switch was on lets later steps in the same session know the feature was used, even if it has since turned off.\n\n- Flag `tengu_nankeen_kestrel`: Off in both readings (read for one account on one subscription tier against v2.1.310; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Windows\n- Names: `CLAUDE_CODE_NANKEEN_KESTREL`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}