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_TOKENwith no other credential source present, in addition to its existing check. - The diagnostic message shown when
ANTHROPIC_UNIX_SOCKETis set was reworded to explicitly state whetherCLAUDE_CODE_OAUTH_TOKENis 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed org policy being fetched through, and rejected by, third-party local proxies set via ANTHROPIC_UNIX_SOCKET; they are again treated…