feat(server): resume usage-limited threads automatically - #1
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:24899876fc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const scheduleUsageLimitResume = useAtomCommand(threadEnvironment.scheduleUsageLimitResume, { | ||
| reportFailure: false, | ||
| }); | ||
| const cancelUsageLimitResume = useAtomCommand(threadEnvironment.cancelUsageLimitResume, { |
There was a problem hiding this comment.
This wires schedule/cancel controls only into the web ChatView; a repo-wide search of apps/mobile finds no consumer of usageLimitResume, scheduleUsageLimitResume, or cancelUsageLimitResume. When the server automatically schedules a retry, mobile users therefore cannot see that pending state or explicitly cancel it without switching clients, despite the shared contract exposing the feature to every client. Add equivalent status and cancellation handling to the mobile thread surface.
AGENTS.md reference: AGENTS.md:L70-L73
Useful? React with 👍 / 👎.
| When Codex, Claude Code, Cursor, Grok, or OpenCode reports that a thread has reached its usage | ||
| limit, the thread error includes **Resume when available**. Select it to let T3 Code continue the | ||
| same thread automatically after usage becomes available again. T3 Code never creates a new thread |
There was a problem hiding this comment.
For typed usage-limit runtime errors, ProviderRuntimeIngestion immediately dispatches thread.usage-limit-resume.schedule without UI opt-in, after which the web action is labeled Cancel auto-resume. These instructions instead tell affected users to look for and select Resume when available, an action that normally disappears as soon as the automatic schedule is projected. Document that scheduling is automatic and describe cancellation rather than requiring a nonexistent opt-in step.
Useful? React with 👍 / 👎.
This builds on pingdotgg#8577 and makes automatic resume dependable without requiring the user to opt in first.
Usage-limit, workspace spend-cap, and model-capacity errors now start the durable resume schedule on the server. Provider reset timestamps still win. Messages such as
try again at 7:41 PMare parsed in local time and scheduled for 7:42 PM. When no reset time is available, retries use three 20-minute waits, five one-hour waits, then six-hour waits.The branch is based directly on the official
v0.0.38tag. It keeps the release's server, web, desktop, and contract changes while rebasing the original PR into one reviewable commit.Mobile compatibility is preserved under version skew. Existing mobile clients receive the normal
runtime.erroractivity with an automatic-resume hint, while new resume-only event tags are withheld from legacy thread-detail streams. Schedule state remains available through the normal thread snapshot.Verification:
Generated with Codex in T3 Code.