top of page


What Is an AI Agent, Really?
Agents, from the ground up · Part 1 of 7 I asked an AI agent to write tests for a security detector. Its first attempt failed. It read the error, fixed its own mistake, ran the tests again, and they passed. I didn't touch a thing. What was actually happening there isn't magic, and you don't need any jargon to understand it. One simple mental model explains every AI agent you'll meet. Once you have it, the buzzwords that come later (subagents, orchestrators, memory, MCP) all s
carocsteads
2 days ago4 min read


Agents vs. Workflows: Not Everything Called an "Agent" Is One
Agents, from the ground up · Part 2 of 7. In Part 1 we defined an agent as a model + a loop + tools. Now for the distinction that cuts through most of the hype. Open any product page today and everything is an "agent." The email summarizer is an agent. The chatbot is an agent. The thing that renames your files is an agent. Most of them aren't, and that's fine. There are two fundamentally different ways to build with LLMs, and knowing which one you're looking at changes how yo
carocsteads
3 days ago4 min read


The Anatomy of an AI Agent: Same Model, Different Job Description
Agents, from the ground up · Part 3 of 7. If an agent is "a model + a loop + tools," what exactly goes into one? Five ingredients, and they demystify the whole thing. When people hear "we have a test-writing agent and a code-review agent," they often picture two different AIs, each trained for its specialty. That's almost never how it works. Open up any agent and you'll find the same five parts. Change those parts, and the same model becomes a completely different worker. The
carocsteads
4 days ago4 min read


Orchestrator and Subagents: A Team of Agents, and Why They Don't Talk to Each Other
Agents, from the ground up · Part 4 of 7. One agent is useful. A coordinated team of them is how agent systems scale. Here's how that team is actually organized. Some tasks are too big for one agent's desk: "audit every detector in the codebase," "write tests for these twelve modules," "research five competitors and compare them." Stuffing all of that into one context window means it fills up with noise, the agent loses track, and everything happens one slow step at a time. T
carocsteads
5 days ago4 min read


Memory vs. Context: The Desk and the Filing Cabinet
Agents, from the ground up · Part 5 of 7. "Memory" is the most overloaded word in AI agents, because it means two completely different things. Let's untangle them. People say "the agent remembered my preferences" and "the agent forgot what we were doing" in the same breath, as if it's one mechanism that sometimes works and sometimes doesn't. It's actually two separate mechanisms, and once you can tell them apart, a lot of confusing agent behavior suddenly makes sense. 1. Cont
carocsteads
6 days ago4 min read


Where Does the Agent Run? Four Ways to Run the Same Brain
Agents, from the ground up · Part 6 of 7. Several "Claude" products sound alike. One question separates them cleanly: where does the agent loop actually run? Chat app, CLI, SDK, Agent SDK, managed agents… the product names blur together fast. But remember Part 1: an agent is a model + a loop + tools. Every one of these products calls the same family of models underneath. What differs is who runs the loop, where it runs, and whose tools it uses. Answer that, and the product li
carocsteads
7 days ago3 min read


The Golden Rule of AI Systems: AI Generates, Deterministic Checks Decide
Agents, from the ground up · Part 7 of 7. If you remember one thing from this whole series, make it this. It's the principle that separates a flaky AI demo from a system you can actually ship. Let the model generate and triage. Let deterministic code decide pass/fail. The model never sits in the final gate. Everything in the first six parts (loops, tools, specialists, subagents, memory) is about making agents more capable. This part is about making them trustworthy. Those are
carocsteads
Nov 94 min read


Guardrails: How to Build Secure AI Agents (Lessons from FinBot CTF)
Agents, from the ground up · Bonus. Everything I've learned about keeping agents safe from building and testing an AI-security CTF, with no challenge spoilers. FinBot is the OWASP GenAI Security Project's agentic AI capture-the-flag app, built as part of its Agentic Security Initiative (think "Juice Shop for agentic AI"). It simulates a financial-services company as a multi-agent system for vendor management: an orchestrator agent coordinates a team of LLM-powered specialists
carocsteads
Nov 815 min read


Agents Testing Agents: How I QA Multi-Agent Systems Without Letting AI Grade Its Own Homework
Agents, from the ground up · Bonus. A QA engineer's playbook for testing multi-agent apps, using a team of AI agents as testers and plain code as the referee. Here's the uncomfortable truth about multi-agent apps: the traditional testing playbook doesn't fit them. You can't write a test for every path, because the agents choose the path at runtime. You can't enumerate the inputs, because the input is human language. And the worst bugs don't live inside any one agent. They liv
carocsteads
Nov 77 min read
bottom of page