Gateway credential handling reuses pinned entries and gives clearer errors for bad base URLs.
What's wrong with this entry?
With CLAUDE_CODE_USE_GATEWAY set, credential handling now runs in its own step before the normal path: it reuses an already-pinned entry when the token matches instead of re-pinning on every call, keeps the previously pinned URL, and reports a bad ANTHROPIC_BASE_URL as a typed error rather than a generic one. Two new messages explain the pin store refusing a credentials file that is a symlink or unreadable.
- Requires
CLAUDE_CODE_USE_GATEWAYtogether withANTHROPIC_BASE_URLandANTHROPIC_AUTH_TOKEN. - The existing warning for a missing base URL or auth token is unchanged.
gateway TLS pin store refused: the credentials file is a symlink
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.219
Remote Control now explains exactly which endpoint setting blocks it
Both mention base
-
v2.1.238
CLAUDE_CODE_ARTIFACT_SYNC_BASE_URLenv var for artifact syncBoth mention base
-
v2.1.227
claude gatewaynow identifies itself as the gateway providerBoth mention gateway