fix(chat): preserve selected effort and avoid submit usage delays - #514
Merged
Conversation
astyfx
requested review from
paul-seo73 and
png-1105
and removed request for
a team
September 8, 2026 03:39
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
935e705 |
2026-09-08 03:41 UTC | 0 | 0 | 0 |
c36c538 < |
2026-09-08 03:53 UTC | 0 | 0 | 0 |
Last scanned: c36c538 · 2026-09-08 03:53 UTC
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
935e705 |
2026-09-08 03:41 UTC | 0 | 0 | 0 |
935e705 |
2026-09-08 03:41 UTC | — | — | — |
c36c538 < |
2026-09-08 03:53 UTC | 0 | 0 | 0 |
Last scanned: c36c538 · 2026-09-08 03:53 UTC
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Preserve the effort selected in the composer through prompt submission, and run queued prompts with the effort captured when they were queued. Previously, stale draft overrides could replace the displayed effort, while queued items did not retain effort at all.
Avoid a usage-query round trip on every submit: use the latest cached usage below 97%, refresh before dispatch at 97% or above, and immediately block a cached exhausted account. Missing usage refreshes in the background. Queue admission uses cached usage; actual dispatch checks again. Older overlapping usage responses cannot replace newer provider snapshots.
Validation
bun run typecheckpassed.bun run check:max-lines-ratchetandgit diff --checkpassed.Legacy queued items without stored effort retain the prior fallback behavior. This complements the model-switch and migration fixes in #492.