Repository navigation
Conversation
…und waits Queue messages sent while a usage limit blocks the thread, while the provider is compacting, or while the thread is waiting on an awaited command or subagent, instead of starting immediately or leaving the send button stuck.
Do not fold awaited background work into isWorking, which hid the banner and Stop action. Populate pending tasks on mobile detail-derived shells so Queue still works when the shell stream is missing.
Compact is a start_immediately send. Keep it unavailable during background waits even though those waits stay out of isWorking for the Waiting banner.
…er-resume # Conflicts: # apps/mobile/src/state/use-thread-composer-state.ts # apps/web/src/components/ChatView.tsx # apps/web/src/components/chat/ChatComposer.tsx # apps/web/src/components/chat/composerCommandKey.ts
This branch has not been deployed
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
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.
Problem
After a usage-limit stop, during provider compaction, or while a thread is waiting on an awaited command/subagent, follow-ups could not be queued: Send stayed busy, offered Submit/Steer, or started immediately instead of joining the queue.
Expected
Queue follow-ups in those states. They run after the limit continuation, compaction, or background wait finishes. Steer stays unavailable there. The Waiting banner and Stop action remain visible while background work holds the thread.
Approach
queue_after_activewaits behind a usage-limited run when no active run existsisWorking(which would hide the Waiting banner)Web and mobile share the same dispatch rules for one product behavior. Scope is the reported queue regressions; no separate issue was required beyond maintainer direction in this thread.
Test plan
vp run check:changed(format, lint, knip, typecheck, focused tests, react compiler)Model/harness: Composer via Cursor / T3 Code.
🤖 Generated with Claude Code