How I AI

Felix Rieseberg is the engineering lead for Claude Cowork and Claude Code Desktop at Anthropic. He previously spent five years at Slack building developer tools. In this episode, Felix demonstrates how he uses Claude to solve real-life problems: analyzing floor plans to build interactive 3D house walkthroughs, automatically tracking promises he makes on Twitter, and building a $20 hardware device that physically approves Claude actions with a button press.

What you’ll learn:
How to use Claude Cowork to turn a 2D floor plan into an interactive 3D walkthrough where you can move furniture around
The “go one abstraction layer up” philosophy: why you should never manually enter data Claude can find itself
How to use your email as an inventory database for furniture, clothing, and personal purchases
When to use Opus vs. Sonnet 4.6 (hint: it’s about how well you can scope the problem, not technical complexity)
How live artifacts work and why they’re powerful for dashboards that refresh with real-time data from your connectors
The product philosophy behind making latency delightful
How to build your own $20 hardware device using Claude Code (no hardware experience required)
Why Felix never reads the code Claude writes and judges it purely on output
—
Brought to you by:
Magic Patterns—Prototypes that look like your product
Guru—The AI layer of truth
—
In this episode, we cover:
(00:00) Introduction to Felix Rieseberg
(02:40) Felix’s role at Anthropic
(03:25) The multiple tabs in Claude and why they exist
(05:55) Using Claude Cowork to design a new house using floor plans
(09:52) When to use Opus versus Sonnet 4.6
(12:37) Building an interactive 3D furniture planner
(14:30) Using your email as a source of truth for personal inventory
(15:58) The anti-to-do list: going one abstraction layer up
(23:14) Introduction to live artifacts
(26:02) Building a personal dashboard with live data
(28:37) Being polite to Claude (and why it matters for your humanity)
(30:28) Claude interaction tips
(32:33) Looking at the daily dashboard
(33:55) How live artifacts work with connectors
(35:02) Redesigning the dashboard
(37:55) The biggest gap: people don’t know what problems AI can solve
(41:52) The reverse interview
(42:30) Making latency delightful through asynchronous design
(44:05) The redesigned dashboard
(45:28) AI should free up your creative energy
(46:44) Building a $20 hardware Claude buddy
(52:33) Why kids are magical AI users
(54:30) Recap and final thoughts
—
Tools referenced:
• Claude Cowork: https://www.anthropic.com/product/claude-cowork
• Claude Code: https://claude.ai/code
• Claude for Chrome: https://code.claude.com/docs/en/chrome
• Claude Desktop: https://claude.ai/download
• Live Artifacts: https://support.claude.com/en/articles/14729249-use-live-artifacts-in-claude-cowork
• Connectors (Spotify, Gmail, Calendar, Notion): https://claude.ai/settings/connectors
• Slack: https://slack.com/
—
Where to find Felix Rieseberg:
Website: https://felixrieseberg.com/
LinkedIn: https://www.linkedin.com/in/felixrieseberg/
X: https://x.com/felixrieseberg
GitHub: https://github.com/felixrieseberg
—
Where to find Claire Vo:
ChatPRD: https://www.chatprd.ai/
Website: https://clairevo.com/
LinkedIn: https://www.linkedin.com/in/clairevo/
X: https://x.com/clairevo
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Today is day one of Google I/O 2026, and I walk through every major announcement live—from the new Gemini 3.5 model family to Anti-Gravity 2.0, Google AI Studio, Gemini’s consumer redesign, the Omni video model, Flow, Stitch, and Pomelli. I test them in real time and tell you exactly which ones delivered.

What you’ll learn:
How Gemini 3.5 Flash benchmarks against Claude and GPT models on speed and agentic coding tasks
How Anti-Gravity 2.0’s new features (projects, scheduled tasks, subagents, slash commands) compare to Codex and Claude Code
Why the /grill-me slash command could be a more aggressive alternative to Claude Code’s clarification flow—and how to use it
How Google AI Studio’s new Workspace integration is designed to own the internal productivity app use case
How Google’s new creative tools work in practice: Omni (video generation), Flow (cinematic video editing and character consistency), Stitch (streaming UI design with inline edits), and Pomelli (brand identity and asset generation)
Why Google’s launch-to-availability gap is still a problem—and what to do when a featured product doesn’t actually work yet
—
Brought to you by:
Magic Patterns—Prototypes that look like your product
Thoughtspot—Build AI-powered analytics into your product
—
In this episode, we cover:
(00:00) Google I/O 2026 day 1 overview
(01:47) Gemini 3.5 flash
(04:19) Antigravity updates
(06:32) CLI test and agent features
(07:59) Core agent features released today—May 19th, 2026
(09:43) New slash commands
(11:20) Antigravity test results and takeaways
(12:25) AI Studio updates
(13:52) Access issues
(15:20) Gemini redesign
(17:24) Gemini image gen test
(19:16) Omni (video generation)
(22:56) Flow (cinematic editing)
(24:31) Avatar creation test
(26:45) Pomelli and Stitch
(31:13) Recap and final thoughts
—
Tools referenced:
• Gemini 3.5 Flash: https://deepmind.google/technologies/gemini/
• Antigravity: https://antigravity.google/
• Google AI Studio: https://aistudio.google.com/
• Google Gemini: https://gemini.google.com/
• Omni (video generation): https://gemini.google/overview/video-generation/
• Google Flow: https://flow.google/
• Stitch: https://stitch.withgoogle.com/
• Pomelli (Google brand tool): https://labs.google.com/pomelli/about/
—
Other references:
• Google I/O 2026 announcements: https://blog.google/innovation-and-ai/sundar-pichai-io-2026/
—
Where to find Claire Vo:
ChatPRD: https://www.chatprd.ai/
Website: https://clairevo.com/
LinkedIn: https://www.linkedin.com/in/clairevo/
X: https://x.com/clairevo
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Thariq Shihipar is an engineer at Anthropic working on the Claude Code team. He’s spent the past several months experimenting with HTML as a replacement for Markdown in planning and implementation workflows, discovering that richer visual formats lead to better human engagement—and, ultimately, better products. In this episode, filmed at Anthropic’s Code with Claude event in San Francisco, Thariq demonstrates how to use HTML artifacts to create interactive plans, build throwaway UIs for specific problems, and maintain living design systems that travel with your codebase.

What you’ll learn:
Why HTML has replaced Markdown as the ideal format for AI agent communication and planning
How to brainstorm in HTML to get visual mockups and interactive demos instead of text lists
The technique for building throwaway micro-UIs to edit specific parts of your plan
How to create a living design system in HTML that lives in your repo and travels with every project
Why “complexity has to earn its keep” and how HTML helps you stay in the loop without over-constraining Claude
The prompting technique that gives Claude flexibility while ensuring that you get what you need
Why 99% of your AI-generated tokens should go to planning, interfaces, and communication—not production code
—
Brought to you by:
Celigo—Intelligent automation built for AI
Persona—Trusted identity verification for any use case
—
In this episode, we cover:
(00:00) Introduction
(02:39) HTML as the new Markdown
(04:30) The compute allocator mindset
(05:51) How HTML makes specs more engaging
(06:48) Demo: Brainstorming in HTML with Claude Code
(09:24) From brainstorm to full implementation plan
(11:20) Prompting philosophy: Trust Claude but give it constraints
(13:50) The future of PRDs and tech specs
(18:16) Making HTML specs editable
(20:23) The abundance mindset
(24:17) Just-in-time documentation and throwaway software
(25:39) Using plans as artifacts for implementation
(26:39) Demo: Living design systems in HTML
(30:16) Adding comments and annotations to HTML plans
(31:42) Recap: The HTML workflow
(32:21) Lightning round and final thoughts
—
Tools referenced:
• Claude Code: https://claude.ai/code
• Claude Design: https://claude.ai/design
• AWS: https://aws.amazon.com/
• Figma: https://www.figma.com/
• GitHub: https://github.com/
—
Other references:
• Anthropic Code with Claude event: https://claude.com/code-with-claude
• SpaceX partnership announcement: https://www.anthropic.com/news/higher-limits-spacex
• Jevons paradox: https://en.wikipedia.org/wiki/Jevons_paradox
—
Where to find Thariq Shihipar:
Website: https://www.thariq.io/
LinkedIn: https://www.linkedin.com/in/thariqshihipar/
X: https://x.com/trq212
GitHub: https://github.com/ThariqS
—
Where to find Claire Vo:
ChatPRD: https://www.chatprd.ai/
Website: https://clairevo.com/
LinkedIn: https://www.linkedin.com/in/clairevo/
X: https://x.com/clairevo
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Ryan Nystrom is a software engineer at Notion. He joined in December 2024 after Notion acquired Campsite, the team communication platform he co-founded with Brian Lovin. At Notion, he’s been a core builder of Notion AI and the Custom Agents feature launched in February 2026. He manages a team of six to seven engineers while still writing code himself, currently running Project Afterburner, a push to cut Notion’s CI time to a quarter of its current duration.

What you’ll learn:
How to build a Notion AI custom agent that auto-generates your daily standup pre-read by pulling from Slack, GitHub, Honeycomb metrics, and yesterday’s meeting transcript
How to configure subagents and MCP integrations within Notion AI
How Notion’s internal “Boxy” system lets engineers @mention Codex from within Notion comments and get a full pull request with screenshots in 20 minutes
The spec-first development workflow: dictate an idea into Whisper, have Codex format it as a proper spec, commit it to the repo, and let the agent implement and verify it autonomously
Why fast CI is absolutely critical in the age of AI coding agents
How to prompt AI coding agents to defend their reasoning under pushback
Why engineering managers and even senior executives should keep writing code
—
Brought to you by:
WorkOS—Make your app enterprise-ready today
Orkes—The enterprise platform for reliable applications and agentic workflows
—
In this episode, we cover:
(00:00) Introduction to Ryan Nystrom
(02:48) How AI has upended 12+ years of the same working routine
(04:30) Project Afterburner: Notion’s push to cut CI time to a quarter
(09:00) Why high-frequency, high-quality meetings beat lower-frequency standups
(11:10) How automated context surfaces every engineer’s work equally
(12:15) Why cutting meeting prep is a burnout protection mechanism
(14:26) The case for engineering managers writing code
(16:13) Inside “Boxy”: Notion’s internal VM-based background agent system
(20:30) Old World vs. New World code review
(24:51) Prompting Codex from Notion comments
(29:20) The emotions around code review
(31:01) Quick recap
(32:00) Spec-first development: writing and checking agent specs into the repo
(35:10) The spec as changelog: version control for how a feature actually works
(37:53) How engineers’ roles are evolving
(39:00) Lightning round
(45:21) Where to find Ryan
—
Tools referenced:
• Notion AI: https://www.notion.com/product/ai
• Notion Custom Agents: https://www.notion.com/blog/introducing-custom-agents
• Codex (OpenAI): https://openai.com/codex
• Claude Code (Anthropic): https://claude.ai/code
• Honeycomb (observability + MCP): https://www.honeycomb.io
• Whisper (OpenAI voice transcription): https://openai.com/research/whisper
• Slack: https://slack.com
• GitHub: https://github.com
—
Other references:
• How Stripe built “minions”—AI coding agents that ship 1,300 PRs weekly from Slack reactions | Steve Kaliski (Stripe): https://www.chatprd.ai/how-i-ai/stripes-ai-minions-ship-1300-prs-weekly-from-a-slack-emoji
• Notion 3.3 Custom Agents launch (February 24, 2026): https://www.notion.com/releases/2026-02-24
—
Where to find Ryan Nystrom:
X: https://x.com/ryannystrom
LinkedIn: https://www.linkedin.com/in/ryannystrom/
GitHub: https://github.com/rnystrom
—
Where to find Claire Vo:
ChatPRD: https://www.chatprd.ai/
Website: https://clairevo.com/
LinkedIn: https://www.linkedin.com/in/clairevo/
X: https://x.com/clairevo
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].

Claire breaks down the biggest announcements from Anthropic’s “Code with Claude” event and what they actually mean for builders shipping AI products today. From scheduled AI routines to outcome-based agents, multi-agent orchestration, and new memory systems, Claire walks through the features she’s most excited to use immediately—and how they could reshape the future of agentic software.

What you’ll learn:
How Claude Code routines let you automate recurring workflows on schedules or webhooks
What “Outcomes” are and how rubric-based agent grading works
How multi-agent orchestration enables specialized AI teams with different roles and tools
Why Anthropic’s new “Dreams” memory system matters for long-term agent behavior
Why increased Claude Code usage limits are a bigger deal than they sound
How Claire thinks about building practical agentic products today
—
Resources:
• Code with Claude: https://claude.com/code-with-claude
• Claude Code Routines Docs: https://code.claude.com/docs/en/routines
• Define Outcomes Docs: https://platform.claude.com/docs/en/managed-agents/define-outcomes
• Dreams Docs: https://platform.claude.com/docs/en/managed-agents/dreams
• Multi-Agent Docs: https://platform.claude.com/docs/en/managed-agents/multi-agent
• Managed Agent Webhooks Docs: https://platform.claude.com/docs/en/managed-agents/webhooks#supported-event-types
• Codex (OpenAI): https://openai.com/codex
• GitHub: https://github.com
—
Where to find Claire Vo:
ChatPRD: https://www.chatprd.ai/
Website: https://clairevo.com/
LinkedIn: https://www.linkedin.com/in/clairevo/
X: https://x.com/clairevo
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [email protected].