feat(walkthrough): collapse the walkthrough into one edited message - #54
Merged
Conversation
phorcys420
force-pushed
the
phorcys/walkthrough-single-message
branch
from
August 12, 2026 05:13
74cde3b to
9ec618b
Compare
phorcys420
force-pushed
the
phorcys/walkthrough-single-message
branch
from
August 12, 2026 05:16
9ec618b to
8bee1ac
Compare
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.
What
The walkthrough was sending three separate messages (lifecycle
/close+/reopen, the Q&A embed, and the product resources card). This collapses them into a single message that is edited in place through the flow.How
doWalkthroughnow posts one message with three embeds and the first selector:N/A./close+/reopenlifecycle commands, and gains a[Docs]link field per product resource once the product is known.interaction.updateon that same message: it fills the answered field, rebuilds the resources embed on the product step (Coder gets doc links, code-server gets none), swaps in the next question/selector, and on the last step drops the question + selector and pins.[Docs](url)) instead of a separate Components V2 card, so everything lives in one message.Opened by Coder Agents on behalf of @phorcys420.