Rank, 14 days: 301 on the Claude Code sheet
9 people reported
All time, since Sep 18, including 8 thumbs-up on GitHub.
excludedCommands glob stops matching single git commands with a flag before the subcommand
“Every one of these is a single command and matches the glob git * as a plain string.”
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/17408/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
A single command with no pipe, chain or redirect, such as git -C . status, is sandboxed under git * though it was excluded before.
Is this your bug?
File my report- Where
- Sandbox excludedCommands
- Versions
- 2.1.277
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Excluded commands stay sandboxed5 people
Original reports1, newest first
- 2.1.277: excludedCommands "every part must match" also drops single commands carrying a pre-subcommand flag (git -C, -c, --git-dir)#95455