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.299 ·

Windows sandbox setup gains extra checks, and plugin folders added mid-session are handled

Windows sandbox startup runs extra checks, and the sandbox setup is rebuilt when a plugin folder joins a running session

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

Unclear It is not clear whether a plugin folder that joins mid-session on Windows is brought into the sandbox or refused.

What

The sandbox is the walled-off space Claude Code can run commands in, so they cannot reach everything on your computer. When it starts on Windows, it now runs several extra steps:

  • a check that can refuse to use the current working folder
  • deny rules applied through Windows itself
  • a lookup of the current user's status

The sandbox setup is also rebuilt when a plugin folder (the folder of an add-on package that extends Claude Code) joins a session that is already running. Claude Code records the result as installed, rebuild failed, or set at start. Before, nothing happened when a plugin folder joined partway through.

Why

Plugins added during a session are now taken into account by the sandbox instead of being left out of its setup. If you use the sandbox on Windows, its startup behaves differently, so check that your usual working folders are still accepted.

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 whether a plugin folder that joins mid-session on Windows is brought into the sandbox or refused.

See this entry in the whole of v2.1.299 →

Feedback