{"version":"2.1.271","anchor":"grove-config-check-now-gated-behind-an-additional-oauth-scop","canonical_anchor":"anthropic-unix-socket-auth-message-now-checks-for-claude-cod","heading":"OAuth-token checks tightened for Grove config and unix-socket auth","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/grove-config-check-now-gated-behind-an-additional-oauth-scop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### OAuth-token checks tightened for Grove config and unix-socket auth\n\nGrove config fetching and unix-socket auth diagnostics now explicitly account for CLAUDE_CODE_OAUTH_TOKEN\n\n**Unclear.** What 'Grove' configuration is used for is not stated in the finding.\n\n**What**\n\n- 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.\n\n- 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.\n\n**Why**\n\nThis 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.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}