Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.273 ·

API keys sourced from apiKeyHelper now go through model-catalog policy checks

Auth detection now recognizes keys from apiKeyHelper and routes them through the same model-catalog policy check as other auth methods

Group of 2 Under the hood No documentation found Internal Changes
JSON All of v2.1.273
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ModelsArea: what it touches
Internal ChangesKind: in v2.1.273,
Internal ChangesSection of the release

What

  • The function that determines the active authentication type now returns both the auth type and whether the API key came from an apiKeyHelper, and treats a key sourced this way as present even if its actual value is empty or falsy.
  • A new api_key_helper case was added to the logic that decides model-catalog access policy, so it now goes through the same allow_model_catalog policy check that was previously only applied to not_claude_ai_auth. The no-auth-method case also gained API-key-specific served-catalog handling.

Why

This ensures that when an organization supplies API keys via an apiKeyHelper script rather than a static key, Claude Code correctly recognizes that an API key is in use and applies the same model-catalog access policy as it does for other authentication methods.

Read from
Names in the bundleapi_key_helper

See this entry in the whole of v2.1.273 →

Feedback