Unclear Exactly which commands are newly approved or newly sent to a prompt is not settled.
What
Before Claude Code runs a shell command through its Bash tool (the tool Claude uses to run terminal commands), it reads the command to decide whether it can be approved automatically or whether you should be asked first. When a command is too complicated to read with confidence, Claude Code asks you instead of approving it. That reading has changed in these cases:
- Text after a heredoc on the same line: a heredoc is a block of text fed into a command, started with something like
<<EOF. Previously any extra text after its start marker made the command count as too complex. Now a plain pipeline of commands there is accepted, and anything else is still treated as too complex. - Redirects that store a file descriptor in a variable, such as
{fd}>, are now refused by the checker. - A variable set in front of
exportorreadonlygets new handling, and Claude Code says it can't check that variable before the command runs.
Why
This decides which compound shell commands Claude Code approves on its own and which ones it stops to ask you about, so some commands you used to be asked about may now go through, and others may now prompt you.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Exactly which commands are newly approved or newly sent to a prompt is not settled.