How the Claude Code team uses Claude Code

Thariq Shihipar, Sid Bidasaria, Robert Boyce

Talks worth your time · Claude · 2026-10-07 · 22 min · 7 pages

A year ago, using Claude Code meant prompting, giving feedback, and accepting permission prompts. What does it look like now? Thariq Shihipar, Sid Bidasaria, and Robert Boyce on the Claude Code team share how they use Claude Code in their day-to-day work, including why they do most of their coding through Claude Tag, why they give Claude goals rather than tasks, and why they delete harness features as the models outgrow them. They trace how the product expanded from the terminal into a multi-surface tool that incorporates primitives like auto mode, workflows, and routines. They also share what they miss most about their work as developers pre-Claude Code. 0:00 Intro 0:35 - Working through Claude Tag: from tool calls to goals 2:17 - Building on technology that evolves every two months 4:48 - How the Claude Code team uses Claude Code: AskUserQuestion, artifacts, and Claude Tag 6:41 - Running loops and routines remotely 8:52 - How code review inspired dynamic workflows 14:04 - Building Claude Tag with Claude Tag: verification and feedback loops in Slack 18:37 - What they miss about the old way of software engineering Get started with Claude Code: https://code.claude.com/docs/en/overview Follow ClaudeDevs on X for product updates and best practices from the Claude Code team: https://x.com/ClaudeDevs

Generated automatically from the recording's transcript. It's meant to replace re-watching, not the recording itself — verify against the video at the timestamp before quoting formally. Slides belong to the speakers and organisers. Produced with recording-to-pdf.