2 people reported
All time, since Sep 19.
Worktree guard refuses ~ git paths
“In a session that EnterWorktree binds to a worktree, a user ! command fails when it runs git -C ~/<path>.”
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/3803/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 guard refuses git with ~ paths but allows $HOME. In worktree sessions, cd ~/… or git -C ~/… is refused as "computed at runtime"; absolute or "$HOME/…" paths run.
Is this your bug?
File my report- Where
- Bash tool
- Error text
this command changes directory to a location computed at runtime before running git.- Versions
- 2.1.278 to 2.1.291
- Platforms
- macOS
- 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 rewritten git3 people
- Isolation fence skips Bash writes2 people
- Worktree refuses shell-word args3 people