top of page


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


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