Artifact tokens and artifact base URLs no longer leak into processes Claude spawns.
What's wrong with this entry?
The environment handed to spawned processes now drops the artifacts API token and any artifact base URL variable, alongside the OAuth token and subscription vars it already removed.
- A new predicate matches any variable that starts with
CLAUDE_CODE_ARTIFACTand ends with_BASE_URL, and those are deleted. - The presence of such a variable alone is now enough to force the sanitizing path instead of returning
process.envuntouched. - The artifacts token was added to the sensitive-variable list alongside ANTHROPIC_API_KEY and CLAUDE_CODE_OAUTH_TOKEN, and to the set stripped from config-derived env.
- Applies to everyone on this build.
return e.startsWith("CLAUDE_CODE_ARTIFACT") && e.endsWith("_BASE_URL");
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
OAuth token warning no longer tells you to unset the variable
Both mention oauth token
-
v2.1.234
The CLAUDE_CODE_OAUTH_TOKEN login warning can arrive as its own message
Both mention oauth token
-
v2.1.223
Clearer failures when claude.ai project scopes can't be obtained
Both mention oauth token