[Feature]: Recognize USAGE LIMIT and auto-ping when it's back

[murbanowicz]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

We sometimes hit e.g. Claude 5hr window limit when asleep or away.
Would be great of t3code would first of all understand it (I dont think it shows this atm) and auto ping agent when limits are back so it will resume the work.

Proposed solution

As above. Capture limit hit, schedule wake up, wake it up.

Why this matters

For every provider with 5hr window it is extremely annoying.

Smallest useful scope

As described.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[juliusmarminge]

#8401 proposes the same resume-on-usage-reset behavior and offers an existing implementation. Keeping the contributor offer linked here as the duplicate discussion is consolidated.

[oceanapplications]

Do you want a PR? I have one ready.

[MajorBreakfast]

Seeing this a lot. Would be really valuable to have this as a feature.

Claude Code has it BTW

[moritz-mode]

+1

[juliusmarminge]

Implemented in V2

[juliusmarminge]

Thanks for requesting recovery after subscription limits reset. The orchestrator V2 work has now merged in #2829.

V2 exposes provider limit stops as Limited and adds optional auto-resume when the provider reports its reset time. It also supports snoozing limited threads until that reset, so you do not need to keep checking manually.

Closing this as delivered. If a specific part is still missing in a build containing V2, please open a focused follow-up with the provider/version and the behavior you are seeing.