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 ·

Some bash commands with unusual $ expansions now ask for permission

Bash commands with $ followed by non-ASCII text, and some redirect and loop forms, are now too complex to check and prompt you

You'll notice Improvements
JSON All of v2.1.290
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.290,
ImprovementsSection of the release
What

Before running a shell command, Claude Code reads it to decide whether it can be allowed without asking you. That reading is now stricter. These forms are treated as too complex to check, so you are asked first:

  • $ followed by a non-ASCII character, such as an accented letter
  • $ followed by one of #^=~+ and then non-ASCII text, and ${#é...} forms
  • the same cases inside [[ ]] pattern tests
  • redirects that assign a file descriptor (a numbered input or output channel) to a variable
  • a variable set in front of a declaration inside a branch or loop

The reason shown for the first cases is "A $ followed by non-ASCII text in this command can't be checked before it runs".

Why

Some commands that used to run without asking will now prompt you. Those forms could hide what a command really does, so the check no longer passes them.

See this entry in the whole of v2.1.290 →

Feedback