{"version":"2.1.319","anchor":"skills-as-plugins-suppressed-in-sandboxed-worktree-sessions","canonical_anchor":"skills-as-plugins-suppressed-in-sandboxed-worktree-sessions","heading":"Project skills plugins skipped in sandboxed worktree sessions, with new advice","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/skills-as-plugins-suppressed-in-sandboxed-worktree-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Project skills plugins skipped in sandboxed worktree sessions, with new advice\n\nProject .claude\/skills plugins are now skipped after entering a worktree with the Bash sandbox on, and the hint now covers trusted workspaces\n\n**What**\n\nA worktree is a separate working copy of a git repository in another folder. The Bash sandbox limits what shell commands can reach. Claude Code now skips project plugin folders in `.claude\/skills` when the session has entered a worktree and the Bash sandbox is or was on. Before, these were skipped only when the workspace was untrusted.\n\nThe hint shown when a project plugin is skipped has been reworded:\n\n- Before: accept the trust dialog for this workspace, then run `\/reload-plugins`.\n\n- Now: if the workspace is not trusted yet, accept the trust dialog, then run `\/reload-plugins`. If it is already trusted, restart Claude Code in the folder that holds that `.claude` folder.\n\n**Why**\n\nIf you use worktrees with the sandbox on, your project's skills plugins may not load, and the warning tells you how to get them back. The old advice did not help when the workspace was already trusted.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}