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

Claude Code v2.1.287 ·

Plainer wording when a shell command cannot be checked ahead of time

When Claude Code cannot check a shell command in advance, the reason now says that part of the command cannot be checked, not a technical syntax label

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

Before running a shell command, Claude Code tries to read it and work out what it will do. When part of a command is too complex to read that way, the reason Claude Code gives now says "Part of this command (...) cannot be checked in advance". It used to say "Contains shell syntax (...) that cannot be statically analyzed" and name an internal type for the piece it could not read.

Commands that fail to parse at all still give the reason "Parse error".

Why

If you are asked to approve a complicated shell command, the explanation should be easier to understand.

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 settled where this reason is shown, though it is likely the permission prompt.

See this entry in the whole of v2.1.287 →

Feedback