{"version":"2.1.299","anchor":"sandbox-windows-startup-reworked-plugin-directories-join-t","canonical_anchor":"sandbox-windows-startup-reworked-plugin-directories-join-t","heading":"Windows sandbox setup gains extra checks, and plugin folders added mid-session are handled","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-windows-startup-reworked-plugin-directories-join-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Windows sandbox setup gains extra checks, and plugin folders added mid-session are handled\n\nWindows sandbox startup runs extra checks, and the sandbox setup is rebuilt when a plugin folder joins a running session\n\n**Unclear.** It is not clear whether a plugin folder that joins mid-session on Windows is brought into the sandbox or refused.\n\n**What**\n\nThe 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:\n\n- a check that can refuse to use the current working folder\n\n- deny rules applied through Windows itself\n\n- a lookup of the current user's status\n\nThe 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.\n\n**Why**\n\nPlugins 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.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}