Stop Letting AI Agents Run the Whole Workflow
One inbox agent shouldn’t classify, research, score, route, and draft replies in one loose loop. In this video, I build a Mastra workflow that splits sponsor inbox triage into typed steps — bounded model calls where judgment is actually needed, and deterministic guardrails everywhere else. I walk through normalizing and classifying email with explicit schemas, branching from a parent workflow into nested ones, scoring sponsor fit, and inspecting the whole run in Mastra Studio. The point isn’t one giant agent prompt; it’s deciding which parts need model judgment and where the workflow should own control.
Building an AI agent?
I help teams design and ship agentic systems — from architecture to production.
See how I can help
Building a Software Factory: How Much Should You Delegate to the Agent?
A software factory is not all-or-nothing autonomy. I build a read-only Dependabot triage agent in Mastra and show where delegation should start.

I Added ACP to My Mastra Agent So It Can Work in Repos
ACP is the layer that lets my Mastra agent hand real repo work to Claude Code instead of stopping at advice.

Stop Giving Your Agent Every Tool
Large tool catalogs break agent context. Tool search fixes that by letting agents discover and load only what they need.

Harness Engineering: 4 Levers to Diagnose Any AI Agent
Most agent failures aren't model failures. They're harness failures. Here's the 4-lever framework I use to diagnose what broke.
Get new videos and posts by email
Weekly videos on AI engineering, plus deeper dives in the newsletter.
Occasional emails, no fluff.