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 message when a command's effect can't be checked in advance

When Claude Code can't check in advance what a command will run, the reason now reads "What '<command>' starts can't be checked before it runs"

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 so it can apply your permission rules. Some commands run other commands given to them, which makes that check impossible. The reason shown in that case is now shorter:

  • Before: "'' can run its argument as a command, so what it will run cannot be checked in advance"
  • Now: "What '' starts can't be checked before it runs"

Separately, when a guard fails to run and blocks the command, the block now carries some extra information. A guard is a hook, a check you configure to run before commands.

Why

These messages appear when Claude Code stops or questions a command, so you will see the new wording.

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 extra information is added when a guard that could not run blocks a command.

See this entry in the whole of v2.1.288 →

Feedback