16 lessons · about 233 minutes of reading · complete

You have called a model. You have not rendered a graph.

Two shipped agent products, and both are request/response: send, wait, render the answer. A stateful agent graph gives you none of that shape. It emits node transitions, partial state, tool calls awaiting approval, interrupts, and checkpoints you can rewind to — and that is the data your UI has to render. This course is about reading the graph well enough to know which surface each part of it demands, before anyone asks you to design one.

Start lesson one: A graph is not a chain of calls →

Lessons

The whole spine is registered from day one so lesson numbers never shift. Module one is ready; ask your teaching agent for the next module once the reading-a-graph work is in ARTIFACT.md.

Reading a graph

Opening somebody else’s graph definition and knowing, before you write a line of UI, what surfaces it demands.

Interrupts as a first-class primitive

The difference between a review gate you designed and a review gate the runtime enforces.

State, checkpoints and time travel

What persists between supersteps, and what that persistence lets a UI offer that a request/response app never could.

Not being dogmatic

One framework taught you the vocabulary; the job is reading whichever stack a portfolio company already picked.

How to actually get value from this

Run the graph, don’t just read the diagram. An agent graph is easy to nod along to on a whiteboard and surprising the first time you watch what it actually emits. Every lesson ends with something executable or something written down against real output.
Treat the framework as a vocabulary, not a religion. The concrete API here is LangGraph, because it is documented, open-source and widely deployed. The bar is not that you can use it — it is that you can open an unfamiliar team’s agent code and name the interrupt points.
Assume the docs have moved. Every code sample here is dated and linked to the page it came from. When the page disagrees with the lesson, the page wins — and telling your teaching agent about the drift is part of the exercise.

Agent frameworks move fast, and most of the documentation here is written by the vendor that sells the framework. Every claim on these pages links to the page it came from, with a date — if a source has moved on, check the resource list and tell your teaching agent. The API is expected to drift; the primitives are what the course is actually teaching.