Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Bash permission checks now look at the value of leading environment variables

When a Bash command starts with VAR=value, permission matching now checks the value as well as the variable name

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

Unclear It is not clear which values are now accepted or refused, so it is unclear whether commands that used to match a rule might now ask for permission.

What

A Bash command can start by setting an environment variable (a named setting passed to a program), as in VAR=value command. When Claude Code compares such a command against your permission rules, it decides whether that leading prefix can be safely set aside. Before, it decided by checking only the variable's name against a list of allowed names. It now takes both the name and the value into account.

Why

This makes Claude Code stricter about which variable prefixes it treats as safe when matching Bash permission rules.

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 clear which values are now accepted or refused, so it is unclear whether commands that used to match a rule might now ask for…

See this entry in the whole of v2.1.310 →

Feedback