Setting to automatically resume usage-limited threads when the limit resets

[david1asher]

Problem

When a thread hits the provider's session limit, the thread just stops:

You've hit your session limit · resets 1:50pm

To get the work going again I have to come back after the reset and continue it, or remember to click Resume at reset on each limited thread before I walk away. With several threads running, some get missed and sit idle long after the window has reset.

Proposal

Add a setting that resumes usage-limited threads automatically when the limit resets, with no click needed per thread:

• Setting: "Automatically resume threads when usage limits reset" (global, maybe also per provider). When it's on, every thread that stops with a usage limit and a known reset time is armed for resume as if Resume at reset had been clicked.
• Per-thread override: the banner still shows the reset time and offers Cancel auto-resume, so I can opt one thread out.
• Visibility: the stopped-thread notice says it will resume, e.g. "Session limit hit · resuming automatically at 1:50pm".
• Multiple threads: if several threads are waiting on the same reset, stagger them a little so they don't all burn the fresh window at the same moment.

Related

• Feature: schedule resuming when usage resets #8401 / Auto resume on sessions resets. #11003: the original per-thread "resume at reset" request
• [Bug]: "Resume at reset" never fires: banner shows "Cancel auto-resume" but the thread is not resumed after the usage limit resets #17808: Resume at reset doesn't fire after the reset
• [Bug]: Claude usage-limit reset shown in activity but missing auto-resume controls during subagent workflow #15665 / [Bug]: Usage-limited Claude thread is never armed for auto-resume when background-task wake runs finish as completed right after the limit stop #16815: threads that hit the limit but never get armed for auto-resume
• Opt-in bounded auto-resume after transient HTTP 429 without a reset time #16289: bounded auto-resume for 429s that have no reset time

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Thanks for the write-up! This setting already exists: turn on Auto-resume limited threads in Settings (search "auto-resume"; it's server-scoped and also on mobile under Usage limits). Added in #12686, it arms every usage-limit stop with a reported reset time to resume automatically, and each thread can still cancel its own scheduled continuation. It's off by default, which is why threads have needed a manual Resume at reset click.

Closing this as already delivered. If threads still don't resume with the setting on, that's tracked in #17808, #15665, and #16815. If you'd still like staggered resumes or a per-provider toggle, a focused Idea for just that would be welcome.