Repository navigation
fix(chat): keep follow-up motion after /change - #213
Merged
Merged
Conversation
A forked transcript starts with a status note, so the first follow-up looked like the opening user and skipped the pin and fly-in. Treat only an earlier user message as the opening turn.
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
/changeforks the session and prepends a system status note. Follow-up pin and fly-in only ran when there was already more than one user row, so the first follow-up in that transcript skipped the transition.Test plan
pnpm exec vitest runon thread-turns, thread-scroll, conversation-controller, and thread-visibility/changeinto a folder, send a follow-up, and confirm the user bubble still flies in and pins