Claude Usage stuck at 0% "rate limited" while /usage shows 16%/11% (v0.1.11)

[odellllong2]

v0.1.11, macOS 26 (Darwin 25.5.0), Homebrew cask, official api.anthropic.com, Max/Pro via Claude Code OAuth.

Both Claude rings (5-hour + Weekly) are stuck at 0% labelled "rate limited", even right after a fresh sync. The Codex side works fine (49% on 5h) — so it's specific to the Claude usage endpoint.

Claude Code's own /usage, same account/same moment:

• 5-hour: 16% (resets 4h)
• Weekly · all models: 11% (resets 5d)

So the data and the OAuth token are fine (the CLI reads the same Claude Code-credentials Keychain item without issue). The app's Claude usage fetch is erroring and falling back to 0% "rate limited".

• Persists across a clean quit + relaunch (not a stale value — the fresh fetch itself fails).
• refreshInterval is the default 300s, so it isn't real client-side throttling.

Likely the undocumented Claude usage endpoint changed (new weekly-limit structure + new models). Reads like the User-Agent / beta-header / parser case, but Claude-specific.

[ericjypark]

Hi thanks for the bug report! I'll take a look into it!

[ericjypark]

Thanks for the thorough report — root caused. It's a server-side penalty plus a real
CodexIsland bug that kept you stuck in it. Fixed in the next release.

api.anthropic.com/api/oauth/usage has its own rate limiter — account-keyed and
sticky: once tripped (usually by statusline tools/widgets polling it every 30–60s),
it 429s every caller indefinitely until your account leaves the endpoint alone for a
while (anthropics/claude-code#30930).
Your token, scopes, and quota are all fine — the CLI's /usage works because it
doesn't depend on this endpoint, and the penalty is server-side, which is why
relaunching didn't help.

The bug on our side: on a 429, v0.1.11 refreshed the token and probed again — 3
requests per 5 min, forever, against a limiter that needs sustained quiet to reset.
The app now stops on the first 429 and backs off for 15 min.

To get unstuck:

1. Quit CodexIsland and any other Claude usage tool (statuslines, widgets, other
   machines — they all share one account bucket).
2. Wait ~an hour without peeking — every probe restarts the penalty clock.
3. Relaunch on the new release; first fetch is immediate.

You can verify with curl before relaunching — 429 = still penalized, 200 = clear:

TOKEN=$(security find-generic-password -s "Claude Code-credentials" -w \
  | python3 -c "import sys,json; print(json.load(sys.stdin)['claudeAiOauth']['accessToken'])")
curl -s -o /dev/null -w "%{http_code}\n" -H "Authorization: Bearer $TOKEN" \
  -H "anthropic-beta: oauth-2025-04-20" -H "User-Agent: claude-code/2.1.170" \
  https://api.anthropic.com/api/oauth/usage

If an hour of true quiet still gives you 429, tell me — that means something else is
hitting the endpoint. Leaving this open until you confirm recovery.

[LeoMessiFan]

I got 401 response.