{"version":"2.1.295","anchor":"forked-skill-resume-refuses-in-diskless-sessions","canonical_anchor":"forked-skill-resume-refuses-in-diskless-sessions","heading":"Forked skill agents refuse to resume in sessions with no storage","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/forked-skill-resume-refuses-in-diskless-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Forked skill agents refuse to resume in sessions with no storage\n\nA forked skill agent now refuses to resume, with an error, when the session has no storage to check its permission limits\n\n**What**\n\nA skill is a packaged set of instructions Claude can use. Some skills run as a forked subagent, which is a separate helper agent working inside its own permission limits.\n\nWhen Claude Code resumes one of these agents, it reads a stored record of those limits. In a session with no storage at all, it now stops with an error instead of reading on. The message begins \"cannot be checked for a forked-skill scoping record\" and says the session has no storage, so Claude Code is refusing to resume the agent.\n\n**Why**\n\nWithout the stored record, the agent would come back without its permission limits. Refusing keeps it from running with more access than it was given.\n\n- Area: Diskless Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}