fix: show sent desktop messages immediately#3056
Closed
YoungDan-hero wants to merge 1 commit into
Closed
Conversation
Desktop chat waited for the backend's first real event before adding the user's submitted message to the transcript. This made short prompts look delayed whenever the bridge, provider, or model had startup latency. Show the submitted message right away with a pending state so the UI responds immediately. Confirm that message when the first backend event arrives, remove it if the user cancels before confirmation, and mark it failed only when submission fails before the backend has accepted the turn. Add reducer coverage for immediate display, confirmation without duplicates, cancel-before-confirmation, early submit failure, and late submit rejection. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jun 4, 2026
esengine
approved these changes
Jun 9, 2026
esengine
left a comment
Owner
There was a problem hiding this comment.
Reviewed the diff: the fix is correct, focused, and CI is green. Approving for merge.
Owner
|
Thanks for this — the change reviewed cleanly and CI was green. But #3603 just merged into main-v2 and touches the same files ( |
lanshi17
pushed a commit
to lanshi17/DeepSeek-Reasonix
that referenced
this pull request
Jun 11, 2026
Submit rejections were swallowed, leaving an optimistic user bubble that looked delivered while the backend never saw the turn. Mark the bubble failed, append a warning notice, and stop the running indicator when the bridge call rejects before the first backend event; confirmed turns are unaffected. Closes esengine#3056 Co-authored-by: reasonix <reasonix@deepseek.com> Co-authored-by: luffy <1292867089@qq.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
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.
Desktop chat waited for the backend's first real event before adding the user's submitted message to the transcript. This made short prompts look delayed whenever the bridge, provider, or model had startup latency.
Show the submitted message right away with a pending state so the UI responds immediately. Confirm that message when the first backend event arrives, remove it if the user cancels before confirmation, and mark it failed only when submission fails before the backend has accepted the turn.
Add reducer coverage for immediate display, confirmation without duplicates, cancel-before-confirmation, early submit failure, and late submit rejection.