Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

macOS sandbox check gives more detailed answers when a sandbox is already on

On macOS, the check for whether a sandboxed feature can run now returns one of several modes instead of always refusing when a sandbox is already active

Under the hood Internal Changes
JSON All of v2.1.284
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SandboxArea: what it touches
Internal ChangesKind: in v2.1.284,
Internal ChangesSection of the release
What

A sandbox is a restricted environment that limits what commands can reach. On macOS, Claude Code runs a check to decide whether a sandboxed feature can be used. That check now returns more detailed results:

  • person: returned when sandboxing or a network proxy is already on and a newer capability check passes. Before, this case always returned person_sandbox.
  • person_read_rules: returned when read rules conflict.
  • locked: returned on the normal success path.

The check can also report that the feature is unavailable.

Why

A sandboxed feature on macOS may now work inside a session that is already sandboxed, where before it was always turned away.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which feature relies on this check, or what the new capability check behind the `person` mode tests.

See this entry in the whole of v2.1.284 →

Feedback