3 people reported

All time, since Oct 3, including 1 thumbs-up on GitHub.

Bash tool loses PATH

“Some sessions start with a broken Bash tool: every command fails with command not found for ls, grep, date, cut, head, tr.”

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/1958/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

Bash tool loses PATH when login-shell probe times out. On Windows with Git Bash under load, the snapshot stores the Windows-format PATH and every command fails until a new session.

Is this your bug?

File my report
Where
Bash tool
Versions
2.1.286 to 2.1.296
Platforms
Windows

Not quite your bug?

  1. Bash command truncated at 8186 chars11 people
  2. Bash tool halves backslashes14 people

Original reports2, newest first

  1. Windows/Git Bash: if the 10-second login-shell PATH probe times out, the Bash tool loses PATH for the whole session#101279
  2. Windows/Git Bash: shell snapshot silently writes the raw Windows PATH when the PATH probe times out, so ls/grep/date are "command not found" for the whole session#99301

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.