fix(chat): hide the bottom pipeline Stop once the transcript has messages#877
Merged
Conversation
…ages Pipeline sessions showed two Stop buttons once the AI step started producing messages: the thinking-row Stop (added in #874) and the pipeline-stop-area Stop that replaces the composer whenever a pipeline is running. Gate the bottom stop area on the transcript being empty (grouped.length === 0) in addition to the pipeline running. During command-only steps there is no thinking row, so the labeled Stop stays; once messages exist, Stop lives on the thinking row and the normal composer returns in queue mode, letting follow-ups be queued against a running pipeline (the backend already drains them on completion). This also keeps the composer visible on later turns of a completed pipeline session, which previously re-entered the stop-only state. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Matt Toohey <contact@matttoohey.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
1 participant
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
While a pipeline runs, the chat composer was unconditionally replaced by a large labeled Stop button — even after the transcript had messages, at which point Stop already lives on the Thinking row (#874). This left two Stop controls on screen and blocked queueing follow-ups.
grouped.length === 0)🤖 Generated with Claude Code