Feature: Show usage reset countdown timer in status line

[pakjilly-cpu]

Problem

Currently the status line shows usage percentage like:

Usage ███████████████░  92%

But there's no way to know when the usage will reset until you actually hit 100% and get rate limited. At that point, a countdown timer appears (e.g., "Retry in 2m 34s..."), but by then it's too late to pace yourself.

Proposal

Show the remaining time until usage resets directly in the status line, before hitting 100%:

Usage ███████████████░  92% (resets in 2h 13m)

Or alternatively:

Usage 92% · resets in 2h 13m

Why this matters

• Pacing: Users on Max plan can pace their usage if they know how much time remains. ("I've used 90% with 3 hours left — I should save some for later.")
• Planning: Helps decide whether to start a large task now or wait for a reset.
• Transparency: The rate limit countdown already exists when hitting 100%, so the server presumably knows the reset window. Exposing it earlier would be a natural extension.

Current behavior

• Before 100%: Only percentage shown, no time info
• At 100%: Countdown timer appears (1-second granularity), but only after being rate limited

Expected behavior

• Reset countdown visible at all times in the status line, updating in real time

[Astro-Han]

+1. Pacing is impossible when you can only see the percentage without knowing how much time is left in the window.

I built claude-pace to solve exactly this. It shows 5h and 7d usage % with live reset countdowns, plus a pace indicator (⇡⇣) so you can tell if you need to slow down:

Opus 4.6 (12%) ●high | myproject (main) 3f +42 -7
  ██████░░░░ 58% 68k | 5h 31% ⇡4% 2h13m  7d 12% 3d05h

Pure bash + jq, installs as a Claude Code plugin in one command. No API key needed (reads rate_limits from stdin).

That said, having this built into Claude Code natively would be the ideal UX. The data is already in the response payload.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.