Skip to content

Conversation

@Remedy92
Copy link
Contributor

@Remedy92 Remedy92 commented Dec 21, 2025

Summary

This adds a simple weekly pace hint so users can quickly tell if they’re trending low/on‑track/high for the week. It shows a short label plus the delta and a relative run‑out estimate when it’s safe to compute.

User impact

  • In the menu card (and text menu), the Weekly section now includes a single line like:
    • "Pace: Low (-3%) · Lasts to reset"
    • "Pace: On track (+1%) · 2d left"
    • "Pace: High (+8%) · 3d left"
  • Only shown for Codex/Claude weekly usage.

Behavior details

  • Uses weekly reset time and window length to estimate expected usage by now and compare to actual usage.
  • Shows relative ETA if the current pace would run out before reset; otherwise shows "Lasts to reset".
  • Hides the pace line if reset timing is missing or inconsistent (avoids misleading output).

Testing

  • swiftformat Sources Tests
  • swiftlint --strict
  • COREPACK_ENABLE_AUTO_PIN=0 pnpm check

Screenshots

Screenshot 2025-12-21 at 12 32 11

@steipete
Copy link
Owner

Please add some text and screenshots :)

@Remedy92
Copy link
Contributor Author

Please add some text and screenshots :)

Done. Thank you for reviewing :)

@steipete steipete merged commit a679311 into steipete:main Dec 21, 2025
1 check passed
@Remedy92 Remedy92 deleted the feature/weekly-pace branch December 21, 2025 17:27
@PhilETaylor
Copy link
Contributor

my pace disappeared overnight - was the claude outage/change overnight at fault, or the fact my weekly quote renewed?

CleanShot 2026-01-08 at 18 29 11@2x

@PhilETaylor
Copy link
Contributor

PhilETaylor commented Jan 8, 2026

Nevermind Claude told me....

  Here's what's happening:

  Your weekly window resets in 6d 20h, which means only about 4 hours have elapsed since it started.

  - 4 hours / 168 hours (1 week) = ~2.4% of the window elapsed
  - The threshold to show pace is 3%

  Since less than 3% of the weekly window has passed, pace is hidden because there isn't enough data yet to make a meaningful pace calculation.

  When will pace appear? Once ~5 hours have elapsed into the weekly window (when expected usage reaches 3%).

  This is by design - showing pace when the window just started would give misleading information because small variations would appear as huge percentage swings.```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants