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.271 ·

OAuth-token checks tightened for Grove config and unix-socket auth

Grove config fetching and unix-socket auth diagnostics now explicitly account for CLAUDE_CODE_OAUTH_TOKEN

Group of 2 You'll notice Internal Changes
JSON All of v2.1.271
You'll noticeTier: 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.271,
ImprovementsSection of the release

Unclear What 'Grove' configuration is used for is not stated in the finding.

What

  • The function that decides whether to check or fetch "Grove" config now also requires either a specific OAuth scope or a bare CLAUDE_CODE_OAUTH_TOKEN with no other credential source present, in addition to its existing check.
  • The diagnostic message shown when ANTHROPIC_UNIX_SOCKET is set was reworded to explicitly state whether CLAUDE_CODE_OAUTH_TOKEN is also set, clarifying that without it, requests on that socket carry no claude.ai login.

Why

This makes it clearer and more consistent when Claude Code relies on CLAUDE_CODE_OAUTH_TOKEN for authentication, both for internal config fetching and in the diagnostics a user sees.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat 'Grove' configuration is used for is not stated in the finding.

See this entry in the whole of v2.1.271 →

Feedback