{"version":"2.1.283","anchor":"new-error-message-when-a-worktrees-git-files-change-mid-re","canonical_anchor":"new-error-message-when-a-worktrees-git-files-change-mid-re","heading":"Clearer error when a worktree's git files change while being read","tier":"notice","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-error-message-when-a-worktrees-git-files-change-mid-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Clearer error when a worktree's git files change while being read\n\nClaude Code now says when a worktree's git files changed mid-read and suggests trying again, instead of a generic unreadable message\n\n**Unclear.** It is not clear where this message appears, possibly only when setting up remote or cloud sessions.\n\n**What**\n\nA worktree is an extra working copy of a git project that shares the main project's `.git` folder. When the main project's git files change while Claude Code is reading them, it now says: \"This worktree's git files, in its main project's .git directory, changed while they were being read. Try again; if it keeps happening, check what else is changing that .git directory.\" Before, this case showed the generic message that the `.git` directory could not be read.\n\nThe messages for when git is not found also have extra text added at the end.\n\n**Why**\n\nA brief clash with something else changing the git files now gets its own diagnosis and a next step, instead of a vague error.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}