[BUG] /usage fails with OAuth scope error: "user:profile" scope missing
Resolved 💬 3 comments Opened Jan 8, 2026 by sachah Closed Jan 11, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When running /usage in Claude Code v2.1.1 after authenticating via OAuth (browser-based token auth), the command fails with a permission error indicating the OAuth token is missing the user:profile scope.
Steps to reproduce:
- Install Claude Code 2.1.1
- 2. Authenticate using the browser-based OAuth flow (token auth)
- 3. Accept the permissions in the browser tab
- 4. Run
/usagecommand
The issue persists even after:
- Logging out and re-authenticating
- - Deleting auth credentials and re-authenticating
- - - Multiple fresh authentication attempts
This suggests the OAuth flow itself is not requesting the user:profile scope that /usage requires to fetch usage data.
What Should Happen?
The /usage command should successfully display usage information after OAuth authentication. The OAuth flow should request all necessary scopes including user:profile so that the usage endpoint can retrieve user data.
Error Messages/Logs
Error: Failed to load usage data:
{"type":"error","error":{"type":"permission_error","message":"OAuth token does not meet scope requirement user:profile","details":{"error_visibility":"user_facing"}},"request_id":"req_011CWtv7qrn5t6Z2EPUahjca"}
Steps to Reproduce
- Install Claude Code v2.1.1
- 2. Run
claudeto start the CLI - 3. Complete the browser-based OAuth authentication flow
- 4. Click "Accept" on the permissions page in the browser
- 5. Run
/usagein the CLI - 6. Observe the permission error
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.1
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗