How I AI

Everybody is saying, “It’s not the model, it’s the harness,” but almost nobody stops to explain what a harness actually is. So I did. I built one live on the show: a Sentry bug-debugging harness for my company ChatPRD, using the Claude Agent SDK, a custom terminal UI built with the Ink library, and opinionated adapters for Sentry, Linear, GitHub, and Vercel. The harness handles evidence gathering, root-cause analysis, and follow-up artifact creation, all without me needing to type “dear agent, please fix this bug” ever again. I also walk through the architecture, share the code structure, and give you the exact process I used so you can build your own harness for any repetitive, structured workflow in your business.

What you’ll learn:
What a harness actually is
When to build a harness versus when to stick with a general-purpose tool like Claude Code or Codex
How to encode specific permissions into a harness
The three components every harness needs
How I used GPT-5.5 and Claude Opus to build the harness code itself (and where they both initially resisted)
How to structure the artifacts your harness produces so the whole team can use the output
—
Brought to you by:
Bolt.new—Turn your idea into a real product
Customer.io—Build customer engagement campaigns from a single prompt
—
In this episode, we cover:
(00:00) What is an AI harness?
(03:19) When to build a harness
(04:33) Why Claire picked bug triage
(06:00) Why not just use Claude Code?
(07:48) Demo: The custom harness interface
(11:04) Architecture: runs, tasks, tools, and artifacts
(13:44) Building it with Codex and Claude
(15:08) Code map and file layout
(16:51) A look at the code
(19:18) The live investigation result
(21:01) How to build your own harness
—
Tools referenced:
• Claude Agent SDK (Anthropic): https://code.claude.com/docs/en/agent-sdk/overview
• Claude Sonnet 4.6 (model used inside the harness): https://www.anthropic.com/news/claude-sonnet-4-6
• Claude Opus (used to build the harness): https://www.anthropic.com/claude/opus
• GPT-5.5 (Codex, used to build the harness): https://openai.com/index/introducing-gpt-5-5/
• Ink (terminal UI library for Node.js): https://github.com/vadimdemedes/ink
• Sentry (error monitoring): https://sentry.io/
• Linear (project management): https://linear.app/
• GitHub: https://github.com/
• Vercel: https://vercel.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 jordan@penname.co.

Alessio Fanelli, founder of Kernel Labs and co-host of Latent Space podcast, walks us through two very different AI workflows: (1) a fully autonomous coding setup using OpenAI Symphony + Linear, where Linear acts as a state machine and Symphony manages agents through the whole dev lifecycle with zero babysitting; (2) Codex with browser access searching eBay for underpriced Pokémon cards—autonomously browsing, extracting PSA certificate numbers, and flagging deals on $10K–$20K cards for his San Carlos card shop, Merlin Games.

What you’ll learn:
Why “agent manager” is a better mental model than “agent prompter”
Why local Mac Minis don’t scale, and what a cloud VPS unlocks
How to wire Symphony and Linear together as an agent state machine
How to track token costs per task (and what 221 million tokens buys you)
What Glimpse does, and why better agent senses extend autonomous runs
Why your CLAUDE.md probably needs a full purge, not more instructions
How Codex scouts underpriced $10K Pokémon cards on eBay at scale
The new category of small business that AI just made possible
—
Brought to you by:
Firecrawl—Power AI agents with clean web data
Jira Product Discovery—Prioritize with insights, build with confidence
—
In this episode, we cover:
(00:00) Intro
(02:24) Prompter vs. agent manager
(04:31) Live demo: Symphony + Linear
(09:31) Setting up Symphony
(14:15) Purging your skills files
(18:06) The benefits of this system
(19:10) Demo: Using Codex to hunt for Pokémon cards
(24:17) The benefit of AI for small businesses
(28:23) Lightning round
—
Tools referenced:
• OpenAI Codex: https://openai.com/codex
• OpenAI Symphony (open-source framework): https://github.com/openai/symphony
• Linear (project management/agent state machine): https://linear.app
• PSA (Professional Sports Authenticator) grading: https://www.psacard.com
• TCGplayer (card pricing): https://www.tcgplayer.com
• eBay (used for card price scouting): https://www.ebay.com
—
Other references:
• Meta Ray-Ban glasses: https://www.ray-ban.com/usa/ray-ban-meta-smart-glasses
• The Monk and the Riddle by Randy Komisar: https://www.amazon.com/Monk-Riddle-Creating-Making-Living/dp/1578516447/ref=sr_1_1
• The Divine Comedy by Dante Alighieri: https://www.amazon.com/dp/0451208633
• AS Roma (football club Alessio and Claire are both fans of): https://www.asroma.com/en
—
Where to find Alessio Fanelli:
X: https://x.com/FanaHOVA
Latent Space podcast: https://www.latent.space/
—
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 jordan@penname.co.

I’ve been testing every major frontier model release since the start of the year, and when Anthropic dropped Sonnet 5, I wanted more than a vibe check. I got tired of one-off tests I couldn’t repeat or compare over time, so I built something better: the How I AI Bench, a repeatable eval harness I constructed live using Claude Code while recording this episode. I ran Sonnet 5 blind against four other frontier models (Sonnet 4.6, Opus 4.8, GPT-5.5, and Gemini 3 Pro) across PRD quality, prototype generation, agentic task completion, and agent personality. The results were not what I expected.

What you’ll learn:
What Anthropic claims Sonnet 5 improves over Sonnet 4.6, and where the benchmark data actually backs that up
How I built the How I AI Bench in under 45 minutes using Claude Code, starting from my own stored session history
Why I combined human vibe scoring (70%) with LLM as judge scoring (30%) instead of trusting either alone
How to set up a local HTML scoring page so you can rate AI outputs on gut feel and export those scores as JSON
Which model I recommend for PRDs, which for complex prototypes, and which for chatting with an agent daily
—
Brought to you by:
Runway—The creative AI platform for images, video and more
Hyperagent—Deploy fleets of agents that handle real work
—
In this episode, we cover:
(00:00) Sonnet 5 is out
(01:55) What Anthropic claims
(04:02) Why I’m done with one-off vibe checks
(05:05) Building the How I AI Bench live with Claude Code
(07:42) The scoring system
(10:43) Agent voice eval
(11:57) Quick recap
(13:58) Results: The How I AI index leaderboard
(21:21) What I’m improving for the next run
(22:16) Generating a Claire-weighted index
(23:53) Model-by-task recommendations
—
Tools referenced:
• Claude Sonnet 5: https://www.anthropic.com/news/claude-sonnet-5
• Claude Opus 4.8: https://www.anthropic.com/news/claude-opus-4-8
• GPT-5.5 (OpenAI): https://openai.com/index/introducing-gpt-5-5/
• Gemini 3 Pro (Google DeepMind): https://deepmind.google/models/gemini/pro/
• Cursor: https://www.cursor.com/
—
Other references:
• SWE-bench Pro (agentic coding benchmark referenced): https://www.swebench.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 jordan@penname.co.

Eddie Kim is the co-founder and CTO of the payroll and HR platform Gusto, which just crossed $1 billion in revenue and serves more than 500,000 small businesses. Recently he did something most CTOs don’t: he went back to writing code. With three other engineers and one designer, Eddie built Gusto Cofounder, a net-new AI product, from zero code to a tier-one launch in 10 weeks. He walks through how that team actually worked, why they threw out nearly every process, and how anyone can copy the approach.

What you’ll learn:
The trash-can method: how to write, review, and delete a full PR as a product decision instead of a planning doc
The two-tool agent stack behind Gusto Cofounder
The exact “perma-Zoom” setup that replaced standups, retros, and Slack threads for 10 weeks
How a designer with no engineering background hit the 94th percentile for shipping code
The eval-first workflow Eddie uses to fix real customer bugs with Claude Code
How a non-technical leader can prototype an idea to win buy-in, then carry it all the way to production-quality code
—
Brought to you by:
Magic Patterns—Prototypes that look like your product
Jira Product Discovery—Prioritize with insights, build with confidence
—
In this episode, we cover:
(00:00) Intro: five people, 10 weeks
(02:38) The origins of Cofounder
(08:32) Inside the 10-week build process
(12:50) Building with no PMs
(14:38) The “trash can” method
(17:15) The stack architecture
(19:10) Shipping to production from day one
(22:03) How a designer became a top engineer
(29:05) Demo: Cofounder over text and Slack
(31:45) Demo: running a real payroll
(36:26) Live coding with evals in Claude Code
(39:39) Recap: prototype, small team, permission
(43:17) Lightning round
(48:44) Where to find Eddie and Cofounder
—
Tools referenced:
• Gusto Cofounder (early access/waitlist): https://gusto.com/cofounder
• Claude Code (Anthropic): https://claude.ai/code
• Cloudflare Workers: https://workers.cloudflare.com/
• Vercel AI SDK: https://sdk.vercel.ai/
• DX (engineering analytics): https://getdx.com/
• Wispr Flow (voice-to-text): https://wisprflow.ai
• OpenClaw: https://openclaw.ai/
—
Other references:
• Gusto (the main product, “Gusto Classic”): https://gusto.com
• Mindbody (referenced as customer data source): https://www.mindbodyonline.com/
—
Where to find Eddie Kim:
LinkedIn: https://www.linkedin.com/in/edawerd/
—
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 jordan@penname.co.

I put GLM 5.2, the open-weight coding model from Z.AI, through four real tasks inside my actual codebase: a codebase architecture audit, a UI redesign, and a 45-minute autonomous bug-hunting session pulling from Sentry and Vercel logs. Total cost: $3.36 for roughly 6 million tokens, a prioritized bug-fix dashboard I’m actually shipping from, and a landing page redesign that matched Chat PRD’s design system on the first try.

What you’ll learn:
What “open-weight” actually means and why it matters for cost and vendor independence
How to connect GLM 5.2 to Cursor and Claude Code
How it performs on codebase exploration and autonomous architecture summarization in a real production Next.js app
Whether GLM 5.2 can match an existing design system
How the model handles a 45-minute long-running autonomous task
Where GLM 5.2 stumbled 
The actual cost breakdown
—
Brought to you by:
Mercury—Radically different banking loved by over 300K entrepreneurs
—
In this episode, we cover:
(00:00) What open-weight models are and why GLM 5.2 is worth testing
(01:38) GLM 5.2 model overview
(04:02) Capabilities and benchmark results
(06:02) How to set up GLM 5.2 in Cursor
(08:37) How to set up GLM 5.2 in Claude Code
(11:04) Live test 1: codebase exploration and architecture audit on ChatPRD
(12:43) Live test 2: generating an HTML architecture and roadmap page
(16:37) Live test 3: redesigning the How I AI landing page in Cursor
(20:57) Live test 4: 45-minute autonomous task, pulling Sentry errors and Vercel logs
(22:35) Where it struggled
(23:49) My verdict on the output
(25:23) Cost breakdown
—
Tools referenced:
z.ai: https://z.ai
GLM 5.2: https://z.ai/blog/glm-5.2
OpenRouter: https://openrouter.ai
Cursor: https://cursor.com
Claude Code: https://docs.anthropic.com/en/docs/claude-code
Sentry: https://sentry.io
Vercel: https://vercel.com

—
Other references:
SWE-Bench Pro leaderboard (coding benchmark scores referenced in episode): https://www.swebench.com
Frontier Suite and Post-Train Bench (additional benchmarks cited): https://scale.com/leaderboard
Use Claude Code with OpenRouter: https://openrouter.ai/docs/cookbook/coding-agents/claude-code-integration
—
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 jordan@penname.co.