Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Shorter, clearer reasons when a Bash command option can't be checked in advance

Permission prompts for timeout, env, command -p/-v and jobs -x now use shorter wording that names the option that couldn't be checked

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

What

Before running a shell command, Claude Code tries to work out what it will do. When an option makes that impossible, the permission prompt explains why. Those explanations were rewritten to be shorter and to name the option involved:

  • timeout and env wrappers now name the option, for example "'timeout ${u}' can't be checked before it runs". Before: "timeout has an option or value (...) that cannot be checked in advance".
  • jobs -x now reads "What 'jobs -x' starts can't be checked before it runs". Before: "'jobs -x' runs its argument as a command, so what it will run cannot be checked in advance".
  • The command -p and command -v messages are also shorter.

Why

When Claude Code asks you to approve a wrapped command, the prompt now tells you more directly which part it couldn't check.

See this entry in the whole of v2.1.288 →

Feedback