Subprocess Environment Scrubbing / Claude Code v2.1.79

What

A new CLAUDE_CODE_SUBPROCESS_ENV_SCRUB environment variable that, when enabled, strips sensitive credentials from the environment passed to subprocesses (like Bash tool invocations).

Usage

CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1 claude

Details

Removes API keys, OAuth tokens, and other secrets from subprocess environments
Scrubbed variables include: ANTHROPIC_API_KEY, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GOOGLE_APPLICATION_CREDENTIALS, AZURE_CLIENT_SECRET, GitHub Actions tokens, and more
Also scrubs INPUT_ prefixed variants of all listed variables

Evidence

Environment scrubbing for subprocess execution (search for "CLAUDE_CODE_SUBPROCESS_ENV_SCRUB")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.79 →

The build it came inv2.1.79

18 Mar 2026 · 26 entries, this one is #4.

Either side of it

v2.1.78Older
v2.1.80Newer

Open the release →

Names in this entry

envCLAUDE_CODE_SUBPROCESS_ENV_SCRUB
A hidden --inherit-permission-mode flag lets a spawned session take its permission mode from whatever launched it.
envANTHROPIC_API_KEY
API key sent as X-Api-Key header. When set, this key is used instead of your Claude Pro, Max, Team, or Enterprise subscription even if you are logged in. In non-interactive mode (-p), the key is always used when present. In interactive mode, you are prompted to approve the key once before it overrides your subscription. To use your subscription instead, run unset ANTHROPIC_API_KEY
envAWS_SECRET_ACCESS_KEY
Policy-helper environment scrubbing moved into its own module and now strips more variables
envAWS_SESSION_TOKEN
Remote-delivered policy helpers now require explicit consent and run with a scrubbed environment
envGOOGLE_APPLICATION_CREDENTIALS
Policy-helper environment scrubbing moved into its own module and now strips more variables
envAZURE_CLIENT_SECRET
Read by the bundled Azure Identity EnvironmentCredential (first in the DefaultAzureCredential chain Claude Code uses for Microsoft Foundry, unless AZURE_TOKEN_CREDENTIALS=dev). With AZURE_TENANT_ID and AZURE_CLIENT_ID it signs in as a service principal with this secret, which takes precedence over a certificate path or a username and password.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.