Worktree refuses shell-word args

“In a session isolated by EnterWorktree, a command is refused whenever any of fifteen shell words appears as an argv element — not only as argv[0].”

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/17304/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 refuses commands with shell words as arguments. Words like hash, source, bind or eval as any argv element, even a path or argument value, trigger "runs a string through" refusals.

Is this your bug?

File my report

Where: Bash tool
Error text: This session is isolated in the worktree <worktree>, but this command runs a string through source, which can't be verified to stay inside the worktree.
Versions: 2.1.304
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Worktree guard refuses commands and edits9 bugs

Worktree Bash refusals12 people
Worktree guard blocks nested repos4 people
Subagent Bash refused after worktree2 people
Heredoc refused in worktree3 people
Empty .git treated as repo root2 people
Worktree guard refuses ~ git paths2 people
Worktree guard refuses rewritten git3 people
Isolation fence skips Bash writes2 people

Original reports2, newest first

Oct 20, 2026Worktree-isolated session refuses ordinary commands whose ARGUMENTS contain the words source or bind ("runs a string through source/bind")#103819
Sep 19, 2026Worktree isolation refuses fifteen shell words in any argv position, including in read-only commands containing no git#95611