# John Bai - The Grok Bot design journey Page: https://stenobird.com/podcast/dive-club-6354915/john-bai-the-grok-bot-design-journey Text version: https://stenobird.com/podcast/dive-club-6354915/john-bai-the-grok-bot-design-journey.md Podcast: [Dive Club 🤿](https://stenobird.com/podcast/dive-club-6354915) Published: 2026-08-25T12:54:03+00:00 Episode link: https://rss.com/podcasts/diveclub/3095326 Audio file: https://content.rss.com/episodes/207227/3095326/diveclub/2026_08_25_12_49_14_2f21d336-ff6f-468c-81cc-44f92e04d5c6.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/dive-club-6354915/episodes/john-bai-the-grok-bot-design-journey Duration seconds: 2904 ## Resource Grok Bot has been going viral the last two weeks so this week's episode is a behind-the-scenes of the design journey with John Bai (who was the first NYC design hire at Cursor). He screen-shares a ton of agent interaction pattern ideas as well as his unused concepts for the Grok Bot onboarding flow. Some highlights: - The prototype that led to the Grok Bot mascot - Why John realized chat was still the right UX for AI - How John uses agents to streamline his Figma work - Comparing John's onboarding concepts for Grok Bot - Why John still starts his design explorations in Figma - What it took to turn AI agents into a consumer product - Why no two designers at Cursor have the same tools/process - + a lot more Ridd mentioned Colin Dunn ’s episode ("informed simplicity") ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/dive-club-6354915/episodes/john-bai-the-grok-bot-design-journey/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/dive-club-6354915/john-bai-the-grok-bot-design-journey.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.