[BUG] rate_limits field still missing/null from statusLine JSON on 2.1.141 (OAuth Pro, firstParty)
Filing as a fresh report because the prior reports of this bug are closed and locked: #40094 (closed not_planned on 2026-05-01, locked by stale-bot) and #45133 (closed as duplicate of #40094). The bug is still live on 2.1.141 with newer evidence.
What's wrong
The rate_limits field is null (was previously absent on older builds — same effective bug) in the JSON piped to the statusLine command, even on an OAuth Pro plan with apiProvider: firstParty. Per the v2.1.80 changelog and the statusLine docs, it should populate after the first API response.
Captured live statusLine JSON (top-level relevant fields, redacted):
{
"version": "2.1.141",
"model": {"id": "claude-opus-4-7", "display_name": "Opus 4.7"},
"rate_limits": null,
"context_window": {"used_percentage": 13, "total_input_tokens": 128657}
}
total_input_tokens=128657 confirms many API calls have already happened in this session — this is not a pre-first-call empty state.
Auth
authMethod: oauth_token,apiProvider: firstParty- Plan: Claude Pro
- OAuth scopes:
user:file_upload,user:inference,user:mcp_servers,user:profile,user:sessions:claude_code
Steps to reproduce
- OAuth-authenticate on Pro/Max (
claude login). - Configure a
statusLinecommand that dumps stdin to a file. - Run any prompt to ensure API calls happen.
- Inspect the dumped JSON:
rate_limitsisnull(or absent on older builds).
Versions
- Claude Code: 2.1.141 (also reproduces on 2.1.142)
- OS: macOS (Darwin 25.4.0)
Why this matters
Without rate_limits, statusline scripts must fall back to /api/oauth/usage, which has aggressive per-token 429 rate limiting (~5 req before lockout). The native field was the intended escape hatch; with it gone, statuslines either show nothing or burn user OAuth quota polling.
Related
- #40094 (closed not_planned, locked) — prior report on 2.1.86
- #45133 (closed duplicate, locked) — same bug on 2.1.96
- #38335, #38350 — possibly correlated server-side rate-limit changes (per #40094 reporter)
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗