Repository navigation
Snooze threads until provider limits reset #31072
daniel-inderos
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
I'd like this option before I hit the limit too. I often know a task will burn through what's left of the 5-hour window, so I'd rather park it now and have it start right after the reset than start it, watch it fail on the limit, and then snooze it from the banner. Could the option show whenever the provider reports a reset time, not only when it's at 100%? When the provider isn't exhausted there's no "last window" to wait for, so it would need to name which reset. For example:
The rest of your design would stay the same: it's an ordinary snooze with a computed time, so no server or contract changes. When the provider is out of usage, your current behavior (wait for the last exhausted window) would still win. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
When a provider is out of usage, I want to park its threads until it can run again. Today that means checking the reset time on the Usage page and choosing a snooze preset or Custom… time that roughly matches, once per thread.
Snooze until reset already exists, but only in the banner of a thread that has already failed on a usage limit. You can't use it before a thread fails, and you can't use it on several threads at once.
Proposal
Add Until limits reset (reset time), for example "Until limits reset (3:21 PM)", to the top of the existing Snooze submenu whenever the thread's provider and model are out of usage:
exhaustedUsageWindow.Before/after, with the same thread and the provider at 100%. These use a dev server and test data, with the replay provider forced to 100% by a local patch:
mainI also checked it on a real Codex account at 100% of its weekly limit. The menu showed "Until limits reset (Sun 8:33 AM)", which matched the reset on the Usage page. Snoozing moved the thread to Snoozed, and Wake thread now brought it back.
Implementation
I have a working branch with tests and a user-docs line: daniel-inderos/t3code@main...feat/snooze-until-limits-reset
Mobile is not included yet. Its thread list strips usage data from providers to avoid re-renders, so I'd like your direction before adding it there. It could be part of this change or a follow-up.
Related: #18949, which is about continuing on another account instead of waiting.
Does this direction and scope work for you? If so, I'll open the PR.
All reactions