Skip to content

Build an agent that can keep improving

Engineering field guide · Agent systems · Both days

What should persist between agent runs?

Connect traces, memory, triggers, and recovery. Then use that feedback to improve the model as well as its runtime context.

All topic guides · Practical takeaways

The talks connect agent quality to a feedback loop. Traces, saved state, and human decisions give the next run information the previous run lacked.

Session Approach
Arize AI · Day 1 Signal reads traces and proposes fixes. Issues and learned skills persist while temporary access is removed after each run.
Google DeepMind · Day 2 Focuses on managed execution: triggers, protected hooks, and credentials kept behind a proxy.
Prime Intellect · Day 2 Extends the loop toward model training. Traces and approvals can become evaluations and training labels.

Arize AI · Day 1 · Google DeepMind · Day 2 · Prime Intellect · Day 2

Persistent memory and model training solve different problems. Training adds data, evaluation, and operating costs. The proposed overnight learning loop is not evidence that every organization benefits from daily training.

  1. Choose a recurring task with a clear trigger and save its run state outside the sandbox.
  2. Interrupt a run and test whether it resumes without repeating completed actions.
  3. Review ten runs and turn one recurring failure into a regression case before changing the agent.

Track duplicate actions, recovery success, repeated mistakes, and time spent reviewing fixes. Use the baseline to decide whether a memory change helps.

The comparison and experiment are our editorial synthesis. They are not a reported benchmark or the speakers’ prescribed procedure.