MoonshotAI / MoonshotAI/kimi-code
feat: Show the absolute reset time alongside the countdown in /usage reset hints
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What feature would you like to see?
The /usage plan usage rows only show a relative reset countdown (e.g. resets in 2h 30m). Even when the platform returns an absolute resetAt timestamp, the CLI computes the diff and discards the actual moment.
For long windows such as the weekly limit, a bare countdown cannot answer "is that this afternoon or tomorrow?" — users have to do the mental conversion themselves.
I'd like the reset hint to show both forms, e.g. resets in 2h 30m (at 14:30), with the absolute moment rendered in the terminal's local timezone. Date context should be graded by distance so a bare clock time is never ambiguous: HH:MM within the same day, MM-DD HH:MM within the same year, YYYY-MM-DD HH:MM across years.
Additional information
The countdown-only format dates back to the first public commit and was never revisited. Existing fallbacks (reset for elapsed windows, resets at <raw> for unparseable timestamps) should be preserved. I have a draft PR ready that implements exactly this and will link it below.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the /usage plan usage rows and the reset-hint formatting path, tracing how resetAt becomes the current countdown and how the existing elapsed and unparseable fallbacks are preserved. Done means displaying both the countdown and a local-time absolute timestamp with HH:MM, MM-DD HH:MM, or YYYY-MM-DD HH:MM precision based on date distance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100