{"version":"2.1.239","anchor":"sandboxed-clis-get-placeholder-credentials-so-they-route-thr","canonical_anchor":"sandboxed-clis-get-placeholder-credentials-so-they-route-thr","heading":"Sandboxed CLIs get placeholder credentials so they route through the agent proxy","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/sandboxed-clis-get-placeholder-credentials-so-they-route-thr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Sandboxed CLIs get placeholder credentials so they route through the agent proxy\n\ngh, aws, gcloud, bq and gsutil get placeholder credentials so they authenticate through the proxy instead of failing.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- 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`.\n- If any real credential variable in a group is already present, no placeholder is injected for that group.\n- The list of credential variables forwarded into the sandboxed environment is now derived from this same table rather than hard-coded.\n\n**Evidence**\n\n`realCredentialEnv`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}