How I AI

Alex Lieberman co-founded Morning Brew in college and grew it into one of the most-read business newsletters in the world before selling it to Business Insider. Now he’s the co-founder and co-managing partner of Tenex. In this episode, Alex explains why distribution is becoming a durable moat, why founders and teams need to “climb Cringe Mountain,” and how he rebuilt his content process around AI without letting it produce generic slop. He walks us through every step of his Content Machine live: an Oracle that scans internal systems and the internet for content spikes, an interview panel that pulls out his real ideas, voice and style files that keep drafts sounding like him, an editorial council that scores and revises posts, and a lessons loop that learns from his feedback.

What you’ll learn:
Why the blank page is the biggest friction point in content creation, and how an AI Oracle eliminates it
How to map your current workflow before you add any AI
How Alex built a six-step Content Machine in Claude that goes from idea spike to publishable post
Why the interview step (not the drafting step) is where AI slop actually comes from
How to codify your voice in a Markdown file so an AI drafts in your register, not the internet’s average
Why your employees are your most underleveraged marketing channel right now
How the Tenex Creator Cup turned content creation into a team sport with a $5,000 prize pool
—
Brought to you by:
Firecrawl—Power AI agents with clean web data
Customer.io—Build customer engagement campaigns from a single prompt
—
In this episode, we cover:
(00:00) Introduction to Alex Lieberman
(02:35) Why Alex built a content machine
(06:56) Alex’s thoughts on AI slop
(09:00) Mapping the workflow from scratch
(13:24) The six-step Content Machine setup
(23:11) Live demo: Oracle, Interview Panel, and Writer’s Council in action
(30:38) Employee advocacy: the Tenex Creator Cup and $5K prize pool
(36:45) Lightning round: great engineers, AI use cases, slop fixes
—
Tools referenced:
• Claude / Claude Code (Anthropic): https://claude.ai
• Wispr Flow (voice-to-text transcription): https://wisprflow.ai
• Notion: https://notion.so
• Linear: https://linear.app
• Slack: https://slack.com
—
Other references:
• Morgan Housel: https://www.morganhousel.com
• David Perell: https://perell.com
• Shaan Puri / My First Million podcast: https://www.mfmpod.com
• Gary Vaynerchuk: https://garyvaynerchuk.com
—
Where to find Alex Lieberman:
X: https://x.com/businessbarista
LinkedIn: https://www.linkedin.com/in/alex-lieberman/
Tenex: https://www.tenex.co/
—
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.

Alex Finn is an AI builder, YouTuber, and the creator of Vibe Code Academy, a community for people learning to build with AI tools. He runs one of the most ambitious local AI setups I’ve come across: three Mac Studio 512 GB machines, a DGX Spark, and a custom RTX 5090 build, all coordinated through a fleet dashboard he built himself. He’s spent five months figuring out which local models belong on which machines, how to wire them to Claude Code loops, and how to get a software factory running without babysitting it.

What you’ll learn:
How Alex chose between a Mac Studio (512 GB unified memory), DGX Spark, and RTX 5090, and what each is actually good for
Why Tailscale is worth installing even on a single machine, and how it lets one agent manage your entire hardware fleet
How the build loop and review loop in Claude Code work
How to allocate tasks by machine and model
Why unlimited local inference changes the use-case math in a way a $20 cloud subscription never can
What OpenClaw and Hermes are each best suited for, and why Alex runs five agents total with failover baked in
—
Brought to you by:
Runway—The creative AI platform for images, video, and more
Jira Product Discovery—Prioritize with insights, build with confidence
—
In this episode, we cover:
(00:00) Intro
(02:58) Alex's hardware stack
(03:48) What "ambient AI" means
(04:15) Alex's red-pill moment with OpenClaw
(07:04) Mac Studio vs. DGX Spark vs. RTX 5090
(13:24) How to set up local models with no technical knowledge (Tailscale + OpenClaw/Hermes)
(17:16) Fleet control dashboard: assigning 24/7 tasks across machines
(20:42) Local models as security scanners feeding Claude Code
(22:25) How Alex allocates GLM 5.2, Qwen 3.6, and Ornith 1.0 by task
(24:28) OpenClaw vs. Hermes: the honest comparison
(26:55) The software factory: build loop, review loop, rocket emoji
(31:55) Lightning round: favorite hardware, favorite model, prompting style
(34:46) Where to find Alex
—
Tools referenced:
• Claude Code: https://claude.ai/code
• OpenClaw: https://openclaw.ai/
• Hermes: https://hermes-agent.nousresearch.com/
• Tailscale: https://tailscale.com/
• Codex (OpenAI): https://openai.com/codex
• GLM 5.2 (z.ai): https://huggingface.co/zai-org/GLM-5.2
• Qwen 3.6 (Alibaba): https://huggingface.co/Qwen/Qwen3.6-35B-A3B
• Ornith 1.0: https://github.com/deepreinforce-ai/Ornith-1
• Gemma 4: https://huggingface.co/collections/google/gemma-4
• Playwright (browser testing): https://playwright.dev/
• Vercel (preview deploys): https://vercel.com/
—
Other references:
• DGX Spark (Nvidia): https://www.nvidia.com/en-us/products/workstations/dgx-spark/
• Mac Studio (Apple): https://www.apple.com/mac-studio/
• How to design AI agent loops: schedules, goals, and subagents in Claude Code and Codex: https://www.lennysnewsletter.com/p/how-to-design-ai-agent-loops-schedules
—
Where to find Alex Finn:
LinkedIn: https://www.linkedin.com/in/alex-finn-1848684a
YouTube: https://www.youtube.com/@AlexFinnOfficial
X: https://x.com/AlexFinn
—
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.

GPT-5.6 Sol is back, and I ran it through my full How I AI vibe benchmark against GPT-5.6 Terra, Luna, Claude Fable 5, and Sonnet 5 across five categories: PRDs, prototypes, wireframes, debugging, and agentic voice. Sol won by a meaningful margin on my Claire Weighted Index (70% my taste, 30% Terminal Bench 2.1), and I also tested two use cases I can't stop thinking about: building a gamified homework tracking app for my kids in one shot with Codex, and browser automation with Chrome that burned through 500 LinkedIn replies while I did literally nothing.

What you’ll learn:
How I scored five AI models (including GPT 5.6 Sol, Fable 5, and Sonnet 5) using my “Claire Weighted Index” benchmark across PRDs, prototypes, code, and agentic voice
The difference between GPT-5.6 Sol (Terra) and Sol for PRD writing
How Fable’s precision and pedantry made it harder to collaborate with, and the exact moment Sol broke through where Fable got stuck
Why Sonnet 5 is still my go-to for agentic voice in OpenClaw, even after this whole benchmark
How I used GPT-5.6 Sol in Codex to build a fully gamified homework tracking app for my kids in one shot
The video editing use case that saved me hours clipping a talk I gave at Cursor’s event
How to use Codex plus GPT-5.6 and Chrome for browser automation, and why this is my single most-loved use case right now
—
In this episode, I cover:
(00:00) Intro
(01:10) The three GPT-5.6 models: Sol, Terra, Luna
(02:17) Pricing: Sol vs. Fable API costs
(03:24) The How I AI benchmark
(05:03) Claire-weighted Index results
(07:00) Per-task winners: prototypes, PRDs, agentic voice
(11:59) What Claire actually rewards
(13:20) Full-fidelity prototype side-by-sides (Sol vs. Fable)
(17:45) Wireframes
(18:19) Agentic voice
(19:15) Where Sol is better than other models
(23:56) Gamified kids’ homework app, built in one shot
(28:02) Fable’s pedantry problem and how Sol broke through it
(31:49) Two bonus use cases: video editing and browser use
(35:08) Final summary and model recommendations
—
Tools referenced:
• GPT 5.6 (Sol, Terra, Luna): https://help.openai.com/en/articles/20001325-a-preview-of-gpt-56-sol-terra-and-luna
• Codex: https://openai.com/codex
• ChatPRD: https://www.chatprd.ai/
• CapCut: https://www.capcut.com/
• Math Academy: https://www.mathacademy.com/
—
Other references:
• Cursor event where Claire spoke on the future of PM: https://www.youtube.com/watch?v=4CAFK-rc26A
• ChatPRD blog (where benchmark outputs will be published): https://www.chatprd.ai/
—
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.

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.