COURSE 001 · FDE ENGINEERING

Engineering Long-Running AI Agents

Ship one customer-shaped AI workflow that is bounded, observable, recoverable, evidence-backed, cost-aware, and useful when the happy path ends.

16 modules · 5 industry cases · 14 optional labs · reference repo

Course content and API examples last verified: 2026-08 · exact dependency versions live in the reference repo lockfile

THE PROMISE

Not merely clever.
Ready to be tested.

The course keeps its technical center: durable state, safe side effects, ownership, recovery, human control, context, observability, security, and evaluation. The FDE layer turns that runtime into one narrow workflow for a real user.

BoundedObservableRecoverableEvidence-backedCost-awareUseful
Open the customer-shaped capstone →

NEW TO PRODUCTION AI?

Watch or read first.
Build only when ready.

You do not need the repository, Docker, an API key, or prior agent experience. Every module explains the failure visually before it introduces the engineering fix.

  1. 1
    UnderstandRead or watch the explanation. No setup.
  2. 2
    TraceFollow the code and failure timeline.
  3. 3
    CheckAnswer one question in your own words.
  4. +
    Build · optionalRun the lab only when you want practice.

THE LEARNING PATH

One system. Four clear stages.

01MODULES 00-02

See the problem

Start with a tiny agent loop. Learn why memory, process state, and model context are not durable state.

02MODULES 03-07

Make it survive

Add checkpoints, safe side effects, worker ownership, recovery, and human approval, one failure at a time.

03MODULES 08-12

Make it governable

Control context, observe behavior, enforce security boundaries, evaluate the path, and build the harness.

04MODULES 13-15

Prove it

Compare real architectures, deploy the runtime, then run every failure together in the production gauntlet.

Industry cases

You build one canonical system, the Vendor Review Agent, all the way through. The concepts are grounded in five industry cases along the way: incident investigation, claims and document workflows, customer operations, enterprise data, and coding agents. One app to build, five systems to understand.

Healthcare

Claims Processing Agent

A document-heavy claims workflow where policy rules, human review, and a complete audit trail are the product, and the model is the smallest part.

documentspolicyhuman review

Financial Services

Enterprise Data Agent

A question-answering agent over enterprise data where the hard problems are permissions, business definitions, and proving the answers are right.

context engineeringdata permissionsSQL

SaaS

Customer Account Agent

An operations agent that acts on customer accounts through real APIs, where every action is a side effect someone has to approve, dedupe, or reverse.

tool permissionsside effectsidempotency

Enterprise Operations

Incident Response Agent

A production investigation agent that fans out across logs, metrics, deploys and tickets, survives partial failure, and synthesizes a defensible incident narrative.

parallel executionpartial failurelong-running agents

Developer Tools

Repository Migration Agent

A coding agent that migrates a large codebase over many sessions, with plans, parallel workers, and verification that does not take "I finished" on faith.

coding agentsplanningrepository context

Course modules

Each module answers one production question. Watch or read to follow the course completely; the labs and the repo are optional depth.

Technologies used

Python

The whole reference implementation; modules 00-02 are plain Python so the loop is visible.

LangGraph

Graph execution, persistence, checkpoints and interrupts, adopted in Module 03 after the failures make them necessary.

PostgreSQL

Durable state, leases, event log, side-effect records. The load-bearing component.

Deep Agents

The higher-level harness Module 12 ports to and interrogates.

FastAPI + HTMX

The run API, review endpoints and operator dashboard, with no frontend framework.

Render + Neon

The free-tier public deployment whose restarts double as failure injection.

Why this stack, in depth →

Optional labs

14 Failure Labs break the running system on purpose: kill the worker, duplicate the publish, poison a page, race two workers. Entirely optional; the lessons describe each failure well enough to learn from without running anything.

Browse the labs

Reference implementation

The Vendor Review Agent lives in an open repo with the fixture server the labs run against. Clone it if you want your hands on the system; skip it if you are here to watch and read.

github.com/ogkranthi/air-course-long

Additional resources

Every module links one to three primary sources with a sentence on why each is worth your time. The full annotated list lives on the course sources page, and the site-wide library is at /resources.

Local progress only: your Watched/Read marks and exit-criteria checklists live in this browser, never on a server.