feat(chat): surface model capacity queue progress on the waiting indicator - #78
Merged
Merged
Conversation
…cator The CLI emits model_queue_status while a request waits for capacity; the plugin now maps it to a model_queue stream chunk and shows the position and estimated wait on the thinking indicator, restoring the usual wording once the request is ready. Older CLIs that never emit the subtype are unaffected. Co-authored-by: QoderAI (Qwen 3.8 Max) <qoder_ai@qoder.com>
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.
Summary
model_queue_statussystem message (SDKSDKModelQueueStatusMessage): the transform layer maps it to a newmodel_queuestream chunk, and the thinking/waiting indicator shows the queue position and estimated wait — e.g.Model is queued (3 ahead · ~12s wait)...— in a warning color, restoring the usual flavor wording once the request leaves the queue.queue_count/wait_time_msare treated as "no data" and not rendered. Nothing is persisted; the status is transient.Verification
npm run typechecknpm run lintnpm run test(170 suites / 3602 tests, incl. 2 new transform cases for both queued and ready mappings)npm run buildnpm run release:checknpm run audit:prodSafety
CHANGELOG.md