Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Bash commands now get their PATH from a new source

Claude Code's saved shell setup now takes its PATH from a new source, falling back to your own, and always adds a guard on pkill

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ShellArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear It is not clear what the new PATH value contains or when it differs from your own.

What

Before running shell commands, Claude Code saves a snapshot of your shell's setup and loads it for every command its Bash tool runs. Three things about that snapshot changed:

  • PATH, the list of folders the shell searches for programs, now starts from a value Claude Code works out itself, and falls back to your own PATH only if that is empty.
  • A replacement for pkill is always included. It refuses patterns that would match Claude Code's own process.
  • A replacement for find and grep is included only when Claude Code ships its own built-in version.
Why

The PATH decides which program runs when a command names one, so this can change which version of a tool every Bash command picks up. The pkill guard stops a command from accidentally killing Claude Code itself.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what the new `PATH` value contains or when it differs from your own.

See this entry in the whole of v2.1.290 →

Feedback