Forumics logo Forumics
Issue 01

Back to issue

All Claude Code known issues

CLAIM C035 Supported 2026-10-31

GitHub issue #79366 in anthropics/claude-code, opened 2026-07-20 by sandopolus, records a report that starting a new session with worktree isolation enabled placed the session inside an existing worktree directory created by a previous session for an unrelated task, with a new branch checked out into the old directory, so the directory name no longer matched the task and leftover files from the previous task could leak into the new task context or pull request.

Verbatim Excerpts from Cited Records
“Starting a new session (new task, worktree isolation enabled) placed the session inside an **existing** worktree directory that a previous session had created for an unrelated task, instead of creating a fresh worktree.”
— sandopolus · anthropics/claude-code (issue 79366 opening body, What happened section) · 2026-07-20T09:33:40Z ·GitHub Issue ↗
“Each new session/task with worktree isolation should get a **fresh** worktree directory named after its own task/branch, created off the default branch.”
— sandopolus · anthropics/claude-code (issue 79366 opening body, Expected section) · 2026-07-20T09:33:40Z ·GitHub Issue ↗
“Leftover untracked/ignored files from the previous task can silently leak into the new task's context or PR.”
— sandopolus · anthropics/claude-code (issue 79366 opening body, Impact section) · 2026-07-20T09:33:40Z ·GitHub Issue ↗
Counter-record: Issue remains open as of 2026-10-30 with 20 comments. Surveyed comments include independent confirmations on macOS and Windows, a worktree lease-registry mechanism discussion, a 2026-10-08 question about whether recent changelog worktree fixes resolved it answered the same day as still reusing on Windows, a 2026-10-21 still-reproducing report on Desktop 3.1623.0 with Claude Code 2.1.304, and a 2026-10-30 note on which leftover file classes carry over. No maintainer resolution appears in the surveyed thread. Falsification probe: If issue #79366 is deleted without archive, if the author edits the opening body so the quoted lines no longer match verbatim, or if the author or maintainers post a definitive retraction showing the described behavior was mischaracterized, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.