Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Shell commands using { ... } after for ((...)) are flagged

Claude Code's shell command reader now flags a { ... } body after for ((...)) and suggests do ...; done

Nothing to try yet In Development
JSON All of v2.1.315
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
In DevelopmentKind: in v2.1.315,
In DevelopmentSection of the release

Unclear What turns the internal check on is not known, so this may not apply to every user.

What

Before running a shell command, Claude Code reads it to work out what it does. It now flags a loop written as for ((...)) followed by a body in curly braces { ... }, and says to write it with do ...; done instead. This only happens when an internal check is on.

Why

Commands written this way may now need your approval, or may be treated as too complex to judge automatically. Writing the loop with do ...; done avoids this.

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 doubtWhat turns the internal check on is not known, so this may not apply to every user.

See this entry in the whole of v2.1.315 →

Feedback