[Bug] Missing `rate_limits` field in statusline JSON payload

Resolved 💬 3 comments Opened Apr 26, 2026 by cynmamani Closed Apr 26, 2026

Bug Description
Bug: rate_limits field missing from statusline JSON payload in 2.1.119 The statusline docs (https://code.claude.com/docs/en/statusline.md) document rate_limits.five_hour.used_percentage and rate_limits.five_hour.resets_at as available fields for Pro/Max subscribers after the first API response. In 2.1.119 the entire rate_limits key is absent from the JSON piped to the statusline command, even mid-session with cost > $0 and many API calls made. The payload only contains: session_id, model, workspace, version, cost, context_window, output_style, effort, thinking, fast_mode, exceeds_200k_tokens. Repro: write a statusline script that dumps stdin to a file, then inspect the dump after a few turns. No rate_limits key appears. Impact: custom statuslines that show 5-hour usage % and reset countdown silently lose that section. Model: claude-opus-4-7[1m], plan: Max.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.119
  • Feedback ID: aa5eb61b-e664-4065-bfbb-1d563c518dba

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/cyn/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n    at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n    at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-26T15:00:18.714Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗