{"version":"2.1.295","anchor":"missing-working-directory-check-and-chrome-skill-message","canonical_anchor":"missing-working-directory-check-and-chrome-skill-message","heading":"Fewer false \"working directory no longer exists\" errors, and clearer Chrome tool gaps","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/missing-working-directory-check-and-chrome-skill-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Fewer false \"working directory no longer exists\" errors, and clearer Chrome tool gaps\n\nClaude Code checks a second time before saying the working directory is gone, and tells the model when some Chrome tools are missing\n\n**What**\n\nThe working directory is the folder Claude Code is running in. When that folder seems to have disappeared and a worktree exists, Claude Code now checks again before reporting that the working directory no longer exists. A worktree is a separate checkout of a git repository. The error appears only if the second check confirms the folder is really gone.\n\nSeparately, the Chrome skill handles a partial set of tools differently. A skill is a packaged set of instructions Claude Code can use. When some of its Chrome tools are available and others are missing, Claude Code logs this and tells the model that the missing tools are unavailable.\n\n**Why**\n\nThe working directory error should now appear less often when the folder is actually still there.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}