What a harness is and how to build one with Claude Agent SDK

How I AI

3 DAYS AGO

Overview Shownote Highlights Transcript Chapters Pins

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