Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Sandboxed CLIs get placeholder credentials so they route through the agent proxy

You'll notice
Useful3 Signal3
Sandbox

gh, aws, gcloud, bq and gsutil get placeholder credentials so they authenticate through the proxy instead of failing.

What

When Claude Code runs gh, aws, gcloud, bq or gsutil inside its proxied environment and none of that tool's real credential variables are set, it now injects placeholder values (literally proxy-injected) so the CLI authenticates via the proxy instead of failing for want of a token.

Details
  • Covered groups: gh uses GH_TOKEN and GITHUB_TOKEN; aws uses AWS_ACCESS_KEY_ID and its companions; gcloud, bq and gsutil use CLOUDSDK_AUTH_ACCESS_TOKEN.
  • If any real credential variable in a group is already present, no placeholder is injected for that group.
  • The list of credential variables forwarded into the sandboxed environment is now derived from this same table rather than hard-coded.
Evidence

realCredentialEnv

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.

See this entry in the whole of v2.1.239 →