[FEATURE] Match claude.ai settings page precision for rate-limit reset countdowns in Desktop App popover

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The rate-limit reset countdowns shown in the Claude Code Desktop App's context-indicator popover (bottom-right of the window) are rendered at coarser granularity than the same values on the claude.ai settings page. Both quotas appear to be subject to the same formatting pattern — only the largest unit is shown, and everything below it is dropped.

In one observed case:

| Quota | Desktop App | claude.ai settings |
|-------|------------|-------------------|
| 5-hour | 2時間後にリセット ("resets in 2 hours") | 2時間48分後にリセット ("resets in 2 hours 48 minutes") |
| 7-day | 6日後にリセット ("resets in 6 days") | 23:59(土)にリセット ("resets at 23:59 on Saturday") |

48 minutes of remaining time in the 5-hour budget were hidden — roughly 16% of the entire window, well outside the territory of harmless rounding. For the 7-day quota the pattern is even more lossy, dropping from an absolute timestamp to a days-only relative count.

This makes it difficult to judge whether a long task — or a final pre-reset run — will fit before the window closes, and forces users to leave the Desktop App and open the web settings page whenever precise reset timing is needed.

Verified in Claude Code Desktop v1.5354.0, macOS 15.7, Japanese UI, Max 5x plan.

Proposed Solution

Align the Desktop App popover with the resolution already shown on the claude.ai settings page in the same locale:

• 5-hour quota: include the minute component (e.g. 2時間48分後にリセット).
• 7-day quota: show the absolute reset timestamp with weekday (e.g. 23:59(土)にリセット), or at minimum hour-level precision plus weekday.

The upstream value clearly carries enough precision — the web settings page already renders it. This appears to be a Desktop-side formatting choice rather than a data limitation.

Alternative Solutions

Opening the claude.ai settings page in a browser whenever precise reset timing is needed. This is a workaround, not a solution: it requires leaving the Desktop App every time I want to make a usage-planning decision.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

1. I open the Claude Code Desktop App with about 2.5 hours of work planned for the rest of the day.
2. I click the context indicator in the bottom-right of the window to check whether the 5-hour quota will reset before I'm done.
3. The popover shows 2時間後にリセット ("resets in 2 hours"). Believing I have only 2 hours, I postpone the most demanding part of the task.
4. Out of curiosity, I open the claude.ai settings page and find that the same window actually had 2時間48分後にリセット (2 hours 48 minutes) remaining.
5. I would have completed the task before the reset; postponing it was unnecessary.

With minute-level precision in the popover, I would have made the correct decision without having to cross-check against the web.

Additional Context

Steps to reproduce the observation:

1. Open the Claude Code Desktop App with an active session.
2. Click the context indicator in the bottom-right of the window.
3. Read the rate-limit reset times displayed in the popover.
4. Open the claude.ai settings page and read the same rate-limit reset times for comparison.

Notes:

• Observed in Japanese locale; behavior in other locales not verified — formatting may differ.
• Plan tier is unlikely to be relevant: any account that surfaces rate-limit information in the popover should reproduce.

Related but distinct prior requests (searched and reviewed before filing):

• #10165 / #11711 — same idea (absolute reset time with weekday, hour-and-minute precision) but for the CLI /usage command and terminal output, not the Desktop App.
• #41739 — countdown timer in the status line, also not the Desktop App popover.
• #41456 — requests rendering the user's statusLine config inside the Desktop App; orthogonal to fixing the existing popover.
• #55376 — requests surfacing the 5-hour window in the Desktop App at all, orthogonal to this precision concern.
• #51222 — reports an incorrect reset value, not a precision issue.

This request specifically targets the precision of the existing context-indicator popover in the Desktop App, which none of the above cover.