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

Claude Code v2.1.239 ·

The same credential threading reaches tool and billing call sites

Billing, artifact, MCP and subagent call sites also take credentials explicitly now.

Under the hood Internal Changes
JSON All of v2.1.239
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
Internal ChangesKind: in v2.1.239,
Internal ChangesSection of the release
What

The explicit credential value also reaches billing and org REST helpers (tax rate, prepaid credits, overage spend limit, admin requests and eligibility, referral eligibility, plugin ratings), design consent and grants, artifact publish/read-back/watch, MCP connect and reconnect, model listing, bug reports, subagent and workflow launches, the OAuth refresh loop, and the tool-use context itself.

Details
  • Also covers project docs read/write/create, plugin install, teleport environment selection, grove policy opt-in, OAuth account switch, history prefetch and session title updates.
  • The org-memory credential minter now refuses a second, different store: handing one in after the fact logs that the later one is ignored.
  • A startup composition path for the policy-limits client reports which of four adoption outcomes occurred, including late composition.
  • Invisible in the common case; the point is that a session can act on a credential set other than the process-global one.
Evidence

{ auth: "teleport-org", timeout: 5000, credentials: n }, credentials, tengu_policy_limits_late_composition, org-memory-discovery: a credentials store was already handed in; the later one is ignored

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

See this entry in the whole of v2.1.239 →

Feedback