{"version":"2.1.301","anchor":"forked-skill-sidecar-scoping-lookup-handles-non-string-trans","canonical_anchor":"forked-skill-sidecar-scoping-lookup-handles-non-string-trans","heading":"Forked skills decide whether they have disk storage in a new way","tier":"internal","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/forked-skill-sidecar-scoping-lookup-handles-non-string-trans","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Forked skills decide whether they have disk storage in a new way\n\nForked skills now work out where their side files are stored, and treat storage as diskless when either location can't be found\n\n**What**\n\nA skill is a packaged set of instructions Claude Code can use, and a forked skill runs separately from the main conversation. Claude Code keeps side files for forked skills next to the conversation's saved transcript.\n\nThe way Claude Code finds those side files has changed:\n\n- It now works from the resolved storage locations rather than a single check.\n\n- If the transcript's location is not a plain file path, it finds the location another way.\n\n- If either side file's location cannot be worked out, the skill is treated as diskless, meaning nothing is saved to disk.\n\n**Why**\n\nThis matters for forked skills when Claude Code runs without saving to disk or uses remote storage.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}