Skip to content

feat(walkthrough): collapse the walkthrough into one edited message - #54

Merged
phorcys420 merged 2 commits into
mainfrom
phorcys/walkthrough-single-message
Aug 12, 2026
Merged

feat(walkthrough): collapse the walkthrough into one edited message#54
phorcys420 merged 2 commits into
mainfrom
phorcys/walkthrough-single-message

Conversation

@phorcys420

@phorcys420 phorcys420 commented Aug 12, 2026

Copy link
Copy Markdown
Member

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

  • doWalkthrough now posts one message with three embeds and the first selector:
    1. Data embed (Category / Product / Platform / Logs), fields start at N/A.
    2. Resources embed (the dynamic second embed): always shows the /close + /reopen lifecycle commands, and gains a [Docs] link field per product resource once the product is known.
    3. Question embed for the current step.
  • Each selection calls interaction.update on 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.
  • Product resource links are now embed fields ([Docs](url)) instead of a separate Components V2 card, so everything lives in one message.

Opened by Coder Agents on behalf of @phorcys420.

@phorcys420
phorcys420 force-pushed the phorcys/walkthrough-single-message branch from 74cde3b to 9ec618b Compare August 12, 2026 05:13
@phorcys420
phorcys420 force-pushed the phorcys/walkthrough-single-message branch from 9ec618b to 8bee1ac Compare August 12, 2026 05:16
@phorcys420
phorcys420 changed the base branch from phorcys/walkthrough-resources to main August 12, 2026 05:16
@phorcys420
phorcys420 merged commit fa695bb into main Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant