Repository navigation
Conversation
While a reply streams, the composer kept the draft but replaced Send with Stop and Enter returned without a word, so a supplement could only be typed in and lost. It is sent now: the server answers 202 with the queued message, the log shows it as queued, and the same stream keeps feeding the replies that follow until the chain ends. Refs ThinkFlowLab#379
github-actions
Bot
requested review from
FayeSpica,
Probiotics5333,
allendyu and
wuzhf9
November 17, 2026 03:24
4 of 5 tasks
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
POST /assistant/messages—202 { queued }goes into the log as a queued bubble with its position, and an idle project streams its reply as before.startframe opens a new reply, anendframe carryingnextTurnIdmeans the next queued message already began, and the finalendcloses the view. Stop follows the chain by trackingnextTurnId, so it stops the reply that is actually running.Depends on #381, which adds
POST /assistant/messages: the endpoint is not onmainyet, so this branch builds and its tests pass on its own, but the browser journeys need that backend to run. Please land #381 first.Linked issue
Refs #379(the same issue as #381; it stays open for runtime-native steering).Refs #379is includedLabels
wtz2333cannot add labels here (GitHub refusesAddLabelsToLabelable). Suggested:type:feat,area:canvas,area:agent.Test plan
node --test tests/*.test.ts→ 834 passed, including the newtests/assistantQueue.test.ts, which covers both answers of the endpoint (202 queued, 200 stream) and a stream that carries two replies.node scripts/check-i18n.mjs→ 3038 keys, 0 problems, Chinese source lines still under the baseline.tsc --noEmit→ clean.vite build→ built.assistant_run_navigation,assistant_sessions,assistant_auxiliary_panels,default_entry,kimi_real) — they need the isolated API and Vite, and [feat] assistant: accept a follow-up message while a turn is still running / 运行中插入补充消息 #379's endpoint to be present, so they run against the merged combination.Evidence that it works
Provider verification
fetch.Bilingual UI
zh-CNanden-USboth gainassistant.panel.queue,queueHint,queued,queueWhileRunningandcancelled.