{"version":"2.1.319","anchor":"skills-in-nested-claudeskills-folders-withheld-when-sandbo","canonical_anchor":"skills-in-nested-claudeskills-folders-withheld-when-sandbo","heading":"Skills in subfolders can be held back until restart while the sandbox is on","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/skills-in-nested-claudeskills-folders-withheld-when-sandbo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Skills in subfolders can be held back until restart while the sandbox is on\n\nWith the Bash sandbox on, skills in .claude\/skills folders below the working folder can stay unloaded until Claude Code restarts\n\n**Unclear.** Whether this is switched on depends on a server-controlled setting whose default is not stated.\n\n**What**\n\nSkills are sets of instructions Claude Code can load from `.claude\/skills` folders. The sandbox limits what Bash commands can reach. While the sandbox is on, or set to hold skills back, Claude Code can now refuse to load skills from `.claude\/skills` folders below the folder it started in or was moved to with `\/cd`. Those skills load only after Claude Code restarts. Claude Code logs a line explaining that sandboxed commands can write to those folders. Skills that Claude Code finds while working are filtered the same way.\n\nThis depends on the `tengu_iridescent_feather` setting, which the server controls.\n\n**Why**\n\nA command running in the sandbox can no longer write a skill into one of those folders and have it loaded during the same session.\n\n- Area: Skills\n- Names: `\/cd`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}