You'll notice
Useful3 Signal3
The wrap-up nudge no longer fires for the 5-hour window or during low-priority mode.
What's wrong with this entry?
Anonymous. No account, no email.
What
The nudge that suggests wrapping up as you approach a usage limit now skips the 5-hour window, and is also held back entirely while the new lower-priority mode is running.
Details
- The scan for crossed usage thresholds takes an extra argument that excludes the
five_hourwindow. - The suppression checks that lower-priority mode is not in its active phase.
- Both are plain code paths with no flag.
Evidence
to continue now at lower priority (counts toward your weekly limit)
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.234
Rate-limit prompts resolve model aliases to the model that actually answers
Both mention rate limit
-
v2.1.234
Quota rejections feed a new auto-resume controller
Both mention rate limit
-
v2.1.242
Lower-priority mode reports extra usage taking over, and shows an allowance percentage
Both mention rate limit