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
HomeReleasesv2.1.242entry #132

Claude Code v2.1.242 ·

OIDC federation tokens get an on-disk cache, with an env override for its location

Federation tokens are cached on disk, and you can move the cache with a new env var.

Use it now Notable No documentation found New Features
JSON All of v2.1.242
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
New FeaturesKind: in v2.1.242,
What probably matters to youSection of the release
What

Setups that federate to Anthropic through an OIDC identity token now cache the resulting federation token on disk, so a token is not re-fetched every time. The directory is created mode 0700 and the location can be pointed elsewhere with the new environment variable CLAUDE_CODE_FEDERATION_CACHE_DIR.

Details
  • The cache file name is derived from a hash of the federation rule id, org, workspace, service account, scope, base URL and the identity token, so a change in any of those uses a different file.
  • Caching is refused, with the reason logged and the session continuing uncached, if the directory is group- or other-accessible, is owned by a different user, if no identity token can be read, or if there is no config directory.
  • Only applies when the auth type is OIDC federation and the environment-variable configuration path is in use.
Evidence

CLAUDE_CODE_FEDERATION_CACHE_DIR

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_FEDERATION_CACHE_DIR
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_FEDERATION_CACHE_DIR

See this entry in the whole of v2.1.242 →

Feedback