{"version":"2.1.299","anchor":"resuming-a-background-subagent-now-refuses-when-its-saved-re","canonical_anchor":"resuming-a-background-subagent-now-refuses-when-its-saved-re","heading":"Some background subagents can no longer be resumed","tier":"notice","area":"Subagents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/resuming-a-background-subagent-now-refuses-when-its-saved-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Some background subagents can no longer be resumed\n\nIn some sessions, resuming a background subagent now stops with a clear message if it was started in a worktree or its saved folder is refused\n\n**Unclear.** Which sessions count as diskless is not stated.\n\n**What**\n\nA subagent is a helper agent that Claude starts to do part of a task. In some sessions, which Claude Code calls diskless, resuming a background subagent now stops before it starts again in these cases:\n\n- its saved record names a folder that is refused: \"Cannot resume this agent in the directory its record names\"\n\n- it was started in a worktree, a separate working copy of a git repository: \"Cannot resume this agent, which was started in a worktree\"\n\n- there is no project folder in reach: \"This agent cannot be resumed from here in this session. Do the rest of the task without it.\"\n\nResuming a forked skill is also refused when the skill's file has not been read since a reload.\n\nBefore, resuming went ahead, checked the worktree and reused it.\n\n**Why**\n\nIf you rely on resuming subagents that ran in worktrees, this can now fail in some sessions. Claude is told to finish the task without that subagent.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}