▶ Watch ↗AI Engineer Europe 20261:15:40
How to Build Agents That Run for Hours (Without Losing the Plot)
Read the full talk →Key ideas
Scroll to read ↓Long-running agents need durable state, testable definitions of done, and critics that use the software. As models improve, the harness must change with them.
- What keeps an agent working after the demo starts?0:15 ↗
- Models and harnesses improve together4:14 ↗
- A loop needs a context policy and an exit7:55 ↗
- Spend context on the work that needs it9:59 ↗
- Turn a vague request into recoverable progress12:05 ↗
- A stronger model changes the necessary machinery14:20 ↗
- Give the critic a different job17:50 ↗
- Write down what good design means20:42 ↗
- Negotiate done before writing code23:42 ↗
- A game maker that looks finished—and one that plays26:46 ↗
- Specific failures make criticism actionable31:19 ↗
- Remove scaffolding when the behavior improves34:14 ↗
- A working music app exposes an evaluation boundary36:39 ↗
- Calibrate reusable judgment, then earn unattended operation40:19 ↗
- Allow a restart without losing the product boundary45:45 ↗
- Evaluate each role and leave a usable history52:01 ↗
- Agent teams can carry the pattern, but the critic needs distance56:21 ↗
- Measure improvement within the product you are building1:01:25 ↗
- Place human review where the application requires it1:07:40 ↗
- Read the trace from the model’s point of view1:13:25 ↗