{"version":"2.1.282","anchor":"claude-code-repo-checkouts-unset-no-default-checkout-when-t","canonical_anchor":"claude-code-repo-checkouts-unset-no-default-checkout-when-t","heading":"No default repository checkout when there is no working folder to use","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/claude-code-repo-checkouts-unset-no-default-checkout-when-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### No default repository checkout when there is no working folder to use\n\nWith `CLAUDE_CODE_REPO_CHECKOUTS` unset, Claude Code no longer assumes a checkout when it cannot work out the current folder\n\n**Unclear.** Which everyday uses of Claude Code reach the case where no working folder can be found is not known.\n\n**What**\n\nWhen `CLAUDE_CODE_REPO_CHECKOUTS` is not set, Claude Code builds a default list of repository checkouts (local copies of a code repository). That list used to always hold one entry pointing at the current directory. Now the entry is only added when Claude Code can actually tell which folder it is working in. If it cannot, the list is empty.\n\n**Why**\n\nThe folder the Claude Code program happened to start in no longer quietly becomes the repository checkout in situations that have no working folder of their own.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_REPO_CHECKOUTS`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}