{"version":"2.1.304","anchor":"fleet-view-auto-mode-eligibility-reasons-reworded","canonical_anchor":"fleet-view-auto-mode-eligibility-reasons-reworded","heading":"Clearer reasons when a folder is not offered","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/fleet-view-auto-mode-eligibility-reasons-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Clearer reasons when a folder is not offered\n\nClaude Code now says when a folder is left out because its repository is never offered, and words the not-a-git-checkout reason more precisely\n\n**Unclear.** Which Claude Code feature shows these reasons is not clear.\n\n**What**\n\nWhen Claude Code leaves a folder out, it gives a reason. Two reasons changed:\n\n- A folder can now be left out because \"it is in a repository that is never offered\".\n\n- A folder that is not a usable git checkout is now described as one where \"it is missing or cannot be opened, or its `.git` is not a plain file or folder\". It used to tell you to start from the top folder of a git repository.\n\nA git checkout is a folder of files tracked with the git version-control tool.\n\n**Why**\n\nThe refusal messages you see are worded differently and say more precisely what is wrong.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}