{"version":"2.1.227","anchor":"claude-rm-tells-you-which-session-is-holding-a-directory","canonical_anchor":"claude-rm-tells-you-which-session-is-holding-a-directory","heading":"claude rm tells you which session is holding a directory","tier":"notice","area":"CLI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/claude-rm-tells-you-which-session-is-holding-a-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### `claude rm` tells you which session is holding a directory\n\nWhen `claude rm` is blocked, it names the session holding the directory and how to stop it.\n\n**What**\n\nWhen removal fails because a directory is still in use, the error now names the cause and tells you to exit the Claude Code session using it, or run `claude stop <id>` if it is a background session, then retry.\n\n**Details**\n\n- Adds an \"occupied\" failure case alongside the existing removal errors, with the blocking session shown above the hint.\n\n**Evidence**\n\n`exit the Claude Code session using that directory (shown above; or 'claude stop <id>' if it is a background session), then run 'claude rm `\n\n- Area: CLI\n- Names: `claude rm`, `claude stop`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}