Unclear Which commands this applies to, and whether it approves more or fewer of them, is not stated.
Some shell commands start by setting an environment variable (a named value the command can read), as in NAME=value command. Claude Code checks these before running them with the Bash tool, the tool it uses to run shell commands. It used to reject such a command whenever a variable failed a single check on its name. For some commands it now rejects only when the variable is not otherwise considered safe and any of these holds:
- the remote switch tengu_umber_plover is off
- a "relaxed" mode is in use
- the fallback for running outside the sandbox (the walled-off area Claude Code can run commands in) has not been closed by a trusted source
tengu_umber_plover falls back to on when the server sends nothing.
This changes which Bash commands that set variables up front can be approved without asking you.
tengu_umber_plover Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.292: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.292. It isn't a statement about your account. What a flag value here can and cannot tell you
Which commands this applies to, and whether it approves more or fewer of them, is not stated.
New in this build: tengu_umber_plover