Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

Windows sandbox refusals now say why an exclusion did not apply

Windows strict sandbox refusals now explain that an exclusion needs an available permission prompt to apply.

You'll notice Improvements
JSON All of v2.1.234
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WindowsArea: what it touches
ImprovementsKind: in v2.1.234,
ImprovementsSection of the release
What

On Windows in strict sandbox mode, a refused command used to give one message regardless of cause. There are now two: the existing one for an exclusion that matched only part of the command, and a new one explaining that an exclusion only exempts a command when a permission prompt could approve running it unsandboxed, and no such prompt is available here.

Details
  • Both paths still refuse the command with the windows_policy_refusal outcome.
  • Applies only on Windows, with sandboxing enabled in settings, the platform in the enabled list, and strict sandbox mode configured.
Evidence

exclusions only exempt a command where a permission prompt can approve the unsandboxed run, and none is available here

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.234 →

Feedback