-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Revert "improvement(mothership): show continue options on abort" #3756
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
icecrasher321
merged 1 commit into
staging
from
revert-3746-improvement/mothership-show-continue
Mar 25, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stoppedblock added to every interrupted message, not just the lastThe removed
resolveInterruptedToolCallswas careful to append thestoppedblock only to the last assistant message and included a dedup guard (!blocks.some((b) => b.type === 'stopped')). The new inline logic unconditionally callsupdated.push({ type: 'stopped' as const })for every message that contains an'executing'tool call.In practice a single stream produces at most one assistant message with live tool calls, so the divergence is unlikely to trigger. But if prior assistant messages somehow retain an
'executing'status (e.g. after a reconnect or partial restore), each of them would receive its ownstoppedblock, potentially rendering duplicate stop indicators in the UI. Adding the same dedup guard keeps the behaviour consistent with the pre-revert code: