Three artifact environment variables are now recognised, with the API token stripped from spawned processes as a secret.
What's wrong with this entry?
Three new CLAUDE_CODE_ARTIFACT* variables are recognised by the CLI, and the token among them is handled as a secret rather than ordinary configuration.
- Added to the recognised env list:
CLAUDE_CODE_ARTIFACTS_API_TOKEN,CLAUDE_CODE_ARTIFACT_ASSET_BASE_URL,CLAUDE_CODE_ARTIFACT_LIVE_BASE_URL. - The asset and live base URLs are plain configuration; the token is classified as a credential.
- As a credential it is stripped from the environment handed to spawned processes, and counted alongside
CLAUDE_CODE_OAUTH_TOKENandANTHROPIC_API_KEY.
CLAUDE_CODE_ARTIFACTS_API_TOKEN
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.227
Two memory-API environment variables are hidden from commands Claude runs
Both mention token base
-
v2.1.227
Groundwork for a development memory backend, unreachable in this build
Both mention token base
-
v2.1.227
Self-hosted memory endpoint is scaffolded but cannot be switched on
Both mention token base