A clock skewed ahead no longer forces your token stats to rebuild on every run.
What's wrong with this entry?
Clock skew that leaves the cache watermark in the future no longer forces a daily token rebuild on every run.
- The rebuild is skipped when the cache's
lastComputedDateis ahead of today, with a debug log explaining why. - Incremental writes now also count
dailyModelTokenswhen deciding whether anything actually changed.
; skipping the dailyModelTokens rebuild until the clock catches up
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit