feat: Support for 5hr 7day rate limit

[Dwtexe]

Added rate_limits field to statusline scripts for displaying Claude.ai rate limit usage (5-hour and 7-day windows with used_percentage and resets_at)

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#2180

[Astro-Han]

The stdin fields you'd need:

rate_limits.five_hour.used_percentage   (float)
rate_limits.five_hour.resets_at         (unix timestamp)
rate_limits.seven_day.used_percentage   (float)
rate_limits.seven_day.resets_at         (unix timestamp)

One gotcha: these fields are null for API users. If you floor a null directly, jq 1.7.1 crashes (null | floor → error). Need a type guard like if type=="number" then floor else null end.

I implemented this in claude-pace (bash+jq) including a pace delta that shows whether the user is burning faster or slower than the window allows. The formatting logic is in claude-pace.sh if it's useful as a reference.

[Haleclipse]

The stdin fields you'd need:

rate_limits.five_hour.used_percentage   (float)
rate_limits.five_hour.resets_at         (unix timestamp)
rate_limits.seven_day.used_percentage   (float)
rate_limits.seven_day.resets_at         (unix timestamp)

One gotcha: these fields are null for API users. If you floor a null directly, jq 1.7.1 crashes (null | floor → error). Need a type guard like if type=="number" then floor else null end.

I implemented this in claude-pace (bash+jq) including a pace delta that shows whether the user is burning faster or slower than the window allows. The formatting logic is in claude-pace.sh if it's useful as a reference.

I have not enabled the use of this parameter yet. Moreover, this segment is inherently ineffective for non-subscribers.

[Dwtexe]

Will this feature be implemented, @Haleclipse?

[ibrahimshadev]

+1 for this. My specific use case: the weekly (7-day) limit is the one I actually ration, but the current usage segment only shows it as the icon fill level — the text percentage is always the 5-hour window. I'd love to see the 7-day percentage as text.

For anyone needing this today, a workaround: ccline writes both utilizations to ~/.claude/ccline/.api_usage_cache.json on each refresh, so a small wrapper script can read seven_day_utilization from there and append it to ccline's output before Claude Code renders it.

It looks like #100 already implements this properly (separate usage_5h/usage_7d segments plus the stdin rate_limits field from Claude Code ≥2.1.80, which would also make it work without extra API polling — related: #112). Would be great to see one of those land. Happy to help test.