Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.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

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaAuthwhat it touches
KindImprovementsin v2.1.271,
Group of 2 You'll notice

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

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
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed org policy being fetched through, and rejected by, third-party local proxies set via ANTHROPIC_UNIX_SOCKET; they are again treated…

See this entry in the whole of v2.1.271 →