Worktree isolation refused

“Agent tool calls with isolation: "worktree" are intermittently refused with a message saying the main checkout's git metadata could not be resolved.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/3249/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Worktree isolation intermittently refused when git probe fails on Windows. Agent tool and EnterWorktree refuse healthy worktrees saying git metadata or identity could not be resolved; retrying later succeeds.

Is this your bug?

File my report

Where: Worktree isolation
Error text: Refusing to use <path> as an isolation worktree: git could not be run
Versions: 2.1.300
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Killed commands leave orphaned processes5 bugs

Orphaned processes after task stop8 people
Orphaned git.exe processes pile up5 people
Hook timeout hangs tool call2 people
Stopping background Bash task leaves child process running, output file grows2 people

Not quite your bug?

Worktree Bash refusals12 people
Worktree guard refuses ~ git paths2 people
Subagent Bash refused after worktree2 people

Original reports2, newest first

Oct 15, 2026Worktree isolation refused as "git metadata that could not be resolved" when git probe exceeds fixed 2000 ms timeout (Windows)#102524
Sep 22, 2026EnterWorktree intermittently refuses a valid, already-registered worktree with "git identity could not be verified"#96195