{"version":"2.1.283","anchor":"agent-tool-refuses-to-start-a-subagent-when-no-working-direc","canonical_anchor":"agent-tool-refuses-to-start-a-subagent-when-no-working-direc","heading":"Subagents are refused when Claude Code has no working folder to give them","tier":"notice","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/agent-tool-refuses-to-start-a-subagent-when-no-working-direc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Subagents are refused when Claude Code has no working folder to give them\n\nIf no working folder can be worked out for a subagent, Claude Code now refuses to start it and tells Claude to do the task itself\n\n**Unclear.** It is not clear which kinds of session end up without a folder to give a subagent.\n\n**What**\n\nA subagent is a helper that Claude starts to handle part of a task on its own. In some sessions, Claude Code cannot work out which folder the subagent should work in. It now refuses to start the subagent there, and Claude is told: \"A subagent cannot be started from here in this session. Do the task without a subagent.\" Claude Code also records the failed launch.\n\n**Why**\n\nClaude gets a clear refusal it can act on and carries on with the task itself. Without the check, the subagent may have run in the wrong folder.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}