
One support desk, every pattern that matters, all of it in real runs.
One question separates them, and it decides cost, speed and risk.
The one building block behind every pattern: a model plus tools, knowledge and memory.
Twelve orders, ten rules, twelve tickets, four tools, and a few traps.
About thirty lines of Python, and no agent framework will look like magic again.
Two model calls, one tool, a correct answer, and the lesson of the attempt before it.
Keep the tools and the rules, hand the loop to the SDK.
Every loop ends. Plan for the times it doesn't end the way you hoped.
Name, description and schema are prompt, not documentation.
An agent recovers from an error it can read, not from one that crashes the loop.
Too thin and the agent makes ten calls. Too fat and it can't use the tool at all.
Reads are cheap mistakes. Writes are expensive ones. Design for the difference.
Fixed steps, structured hand-offs, and checks in code between them.
A small model at the front door, and each ticket goes to a handler built for it.
Twelve labelled tickets turn routing from a guess into a measurement.
Different questions at once, or the same question several times.
Five questions, asked in order, and a combined design for the desk.
A strong model plans the split, small models do the parts, and the merge must not invent.
A focused agent with its own context, tools and model, called like a tool.
The main agent keeps the customer, the subagent answers a context-free question.
One model writes, another grades against a rubric, with a round limit.
Ten searches instead of two, for the same answer, and the costs that never show up in dollars.
Everything the model sees in one call, resent in full at every step.
Continue a conversation, or branch it, without rebuilding the history yourself.
Tools plus storage you own, and rules for when memory is wrong.
The same ticket, the policy in the prompt or behind a search tool.
Assume the agent can be persuaded, and limit what a persuaded agent can do.
The agent proposes the refund. A person decides.
Rules the model can't argue with, and a record of what really ran.
The attack comes from the data. Build as if the model won't resist it.
Fixed tasks, the real agent, graded by code from the trace.
Five full agent runs, graded by code, in under a minute.
What it did, what came back, which guardrails acted, and what it cost.
Eight failures we actually saw, and the rule each one teaches.
Everything from the course, in the order you'd use it.
Most agent demos look impressive for five minutes and fall apart the first time a real user writes something unexpected. This course is about what comes after the demo: the architecture that makes an AI agent predictable, affordable and safe.
You build one system from start to finish: the support desk of a small online bookshop. It reads customer tickets, looks up orders, checks a refund policy and writes replies. Some tickets are simple, some need judgment, and one order hides an instruction that tries to trick the agent into issuing a refund.
What you'll learn:
Workflows vs agents: who decides the next step, and how to choose the simplest shape that works.
The agent loop: built by hand in about thirty lines of Python, then with the Claude Agent SDK, with turn, budget and time limits that really fire.
Tool design: descriptions a model can use, strict schemas, errors as results, and write tools that validate every call in code.
Workflow patterns: prompt chaining with gates, routing with structured output, parallel sectioning and voting.
Multi-agent patterns: orchestrator and workers, subagents with their own context, and an evaluator that grades another model's work.
State and memory: the context window as working memory, sessions that resume and fork, external memory, and retrieval versus preloaded documents.
Guardrails: least privilege, human approval for risky actions, hooks as policy and audit trail, and prompt injection through tool results.
Evaluation and operations: eval suites graded by code, traces for every run, cost per task, and the failure modes to design around.
Real runs, not slides. Every pattern is a small Python program, and every run in the videos was recorded as it happened: each model call, each tool call, each result, and what it cost. Nineteen runs in total, for seventy-one cents at API prices. When a run went wrong, you see that too: an orchestrator inventing facts because its workers lacked context, a subagent searching ten times for something that isn't there, an evaluator that was stricter than the policy, and a memory that overruled what the customer just said. Each failure comes with the design rule that fixes it.
The complete demo project is included as a download: every pattern as its own module, an offline test suite, an eval suite, and all recorded traces.
Recorded with the Claude Agent SDK 0.2.164 for Python, October 2026. About 1 hour 40 minutes in 35 lectures of two to four minutes, each with a short recap and many with a quick question.