Most devs dont understand what agents are @mattpocockuk
Most devs dont understand what agents are  @mattpocockuk
Uploaded October 2025 | Updated September 2026, 2 weeks ago
When OpenAI announced AgentKit, they called it a tool for building agents. But looking at their examples, what they're showing are deterministic workflows with predetermined steps—not true agents. This matters because agents and workflows are fundamentally different patterns for solving different problems.

In this video, I break down:
- What actually makes something an agent vs. a workflow
- Why Anthropic's definition (from their "Building Effective Agents" article) has become the standard
- The key difference: who decides when to stop—the LLM or your code?
- When to use agents (unclear paths, need for improvisation)
- When to use workflows (known solutions, need for optimization)
- Why most real systems exist on a spectrum between the two

Agents are like jazz—improvisation and feel. Workflows are like classical music—optimized upfront for perfect execution. Both have their place, but mixing up the terminology makes it harder to communicate about the trade-offs.

**Resources mentioned:**
- Anthropic's "Building Effective Agents" article: anthropic.com/engineering/building-effective-agents

Join my newsletter on AI Hero:

https://www.aihero.dev/s/y-newsletter

Follow Matt on Twitter

twitter.com/mattpocockuk
Most devs dont understand what agents areYour types cannot hide from the wizard #3console.dir, where have you been all my lifeHeres a NASTY UX problem in most AI-powered appsA dictionary of AI CodingPartial in TypeScript #typescriptBuilding AI Apps That Dont Suck - HandoffsJSDoc vs TypeScript #typescriptNew Skills! /handoff, /prototype, /review and /writing-* | Skills ChangelogYour types cant hide from me #2I Open-Sourced My Own AFK Software Factory5 Claude Code skills I use every single day
Matt Pocock |

Most devs don't understand what agents are

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER