Videos 2IxD9OB3XuQ
Continual Learning for AI Agents: From Failures to Durable Improvements - Soheil Feizi, RELAI
Scene timeline
52 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 207
- whisperx 207
- chunks
- 40
- from 207 cues
- keyframes
- 44
- kept of 52 captured
- frames with text
- 44
- 602 lines read
- chapters
- 0
- from the source metadata
- keyframe bytes
- 4.7 MB
- word timings on 206 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-11 05:15 | 1m 36s |
stt |
done | — | 2026-08-11 05:17 | 22s |
chunk |
done | — | 2026-08-11 05:17 | 0s |
text_embed |
done | — | 2026-08-11 05:17 | 0s |
keyframe |
done | — | 2026-08-11 05:17 | 58s |
ocr |
done | — | 2026-08-11 05:18 | 20s |
frame_embed |
done | — | 2026-08-11 05:18 | 7s |
Frames, and what the machine read
-
- Continual Learning for Al Agents:0.99
- From Failures to Durable Improvements0.99
- Soheil Feizi1.00
- Founder & Chief Scientist, RELAl0.97
- Associate Prof, CS @ University of Maryland0.98
- https://relai.ai1.00
-
- Humans learn from experience.1.00
- Human1.00
- feedback1.00
- act1.00
- World1.00
-
- Humans learn from experience. Agents should too.0.98
- Agent1.00
- feedback1.00
- act1.00
- World1.00
- Continual Learning Loop:0.99
- act → get feedback → improve without forgetting1.00
-
- Continual Learning for an Al Agent0.98
- AGENT1.00
- MODEL1.00
- HARNESS1.00
- MEMORY1.00
- LLM(s): weights1.00
- prompts · skills ·0.94
- in-session state1.00
- model selection1.00
- tools·code·0.95
- persistent1.00
- workflow1.00
- knowledge1.00
- Goal: continuously improve0.98
- the agent from its experiences1.00
- World1.00
- without forgetting.1.00
- users·tools·data0.99
- policies1.00
- Agent logs / outputs0.99
-
- Continual Learning for an Al Agent0.99
- AGENT1.00
- MODEL1.00
- HARNESS1.00
- MEMORY1.00
- LLM(s): weights1.00
- prompts · skills ·0.94
- in-session state1.00
- model selection1.00
- tools·code·0.95
- persistent1.00
- workflow1.00
- knowledge1.00
- Goal: continuously improve0.99
- the agent from its experiences1.00
- World1.00
- without forgetting.1.00
- users·tools·data1.00
- policies1.00
- Agent logs / outputs0.99
-
- Two Challenges in Continual Learning0.99
- AGENT1.00
- MODEL1.00
- HARNESS1.00
- MEMORY1.00
- LLM(s): weights0.98
- prompts · skills ·0.95
- in-session state1.00
- model selection1.00
- tools·code·0.97
- persistent1.00
- workflow1.00
- knowledge1.00
- P2: agent optimization0.98
- Which layer/ components do0.98
- we change, and how?1.00
- World1.00
- users·tools·data0.99
- policies1.00
- P1:gettingfeedback1.00
- Did the agent do well, or what0.97
- Agent logs / outputs0.99
- should it have done instead?1.00
-
- Problem 10.99
- Where does feedback come from?1.00
-
- The easy case: benchmark + evaluator0.99
- Benchmark1.00
- Agent1.00
- Evaluator1.00
- curated task1.00
- runs task0.99
- scores output1.00
- PASS / FAIL / REWARD0.96
- + Feedback0.95
- 81.00
-
- In production, a raw log isn't feedback0.99
- Session log1.00
- An LLM / code analyzes the log0.99
- AUTOMATIC1.00
- A model or eval code reads the trace and writes a critique on what to0.99
- change.1.00
- user: book me a flight to NYC1.00
- Scales to every session1.00
- agent: searching flights...0.96
- agent: called tool get_flights()1.00
- agent: returned 3 options1.00
- A human gives expert feedback0.99
- CRITICAL1.00
- user: none of these work - wrong date0.98
- Domain experts catch what models miss: subtle correctness, policy,1.00
- and taste.0.99
- Lower volume0.98
- Either way, we now have: session log + feedback0.99
- 91.00
-
- But it still isn't testable1.00
- 昌0.63
- What we have0.97
- What we need0.99
- log+feedback1.00
- a replayable learning environment1.00
- "the agent used the wrong date; it should0.99
- A simulation that you can re-run with defined grading on0.99
- confirm dates first."0.99
- thegap1.00
- what success looks like0.98
- 111.00
-
- What is a learning environment?0.99
- An inferred distribution that replays what happened + what success means.1.00
- Observed trace +0.99
- Mocked /real tools0.98
- Synthetic user1.00
- Evaluators1.00
- feedback1.00
- what the agent can call0.98
- whatinteractionrepeats1.00
- whatsuccess means0.99
- whathappened1.00
- The output is executable:0.98
- run candidate agents against it, then keep the fix only if it passes.1.00
- 121.00
-
- What is a learning environment?0.98
- An inferred distribution that replays what happened + what success means.0.99
- Observed trace +0.99
- Mocked /real tools0.98
- Synthetic user1.00
- Evaluators1.00
- feedback1.00
- what the agent can call0.98
- whatinteractionrepeats1.00
- whatsuccess means1.00
- whathappened1.00
- The output is executable:0.98
- run candidate agents against it, then keep the fix only if it passes.1.00
- 121.00
-
- What is a learning environment?0.98
- An inferred distribution that replays what happened + what success means.1.00
- Observed trace +0.99
- feedback1.00
- Mocked /real tools0.98
- Synthetic user1.00
- Evaluators1.00
- what the agent can call0.98
- whatinteractionrepeats1.00
- what success means0.97
- whathappened1.00
- The output is executable:0.99
- run candidate agents against it, then keep the fix only if it passes.1.00
- 121.00
-
- Problem 21.00
- How to optimize the agent?0.97
- 131.00
-
- Three layers to improve the agent1.00
- Model1.00
- SFT · RL post-training0.98
- most expensive0.97
- update the weights0.98
- Harness1.00
- GEPA· trace-to-harness0.98
- mostflexible1.00
- edit prompts, skills, tools, code0.98
- Memory1.00
- Letta1.00
- mem01.00
- consolidation1.00
- cheapest1.00
- store facts and learned skills1.00
- A good learning engine asks for the smallest durable change at the right la0.99
- 141.00
-
- Three layers to improve the agent1.00
- Model1.00
- SFT · RL post-training0.98
- most expensive0.98
- update the weights0.98
- Harness1.00
- GEPA· trace-to-harness0.98
- mostflexible1.00
- edit prompts, skills, tools, code0.98
- Memory1.00
- Letta1.00
- mem01.00
- consolidation1.00
- cheapest1.00
- store facts and learned skills1.00
- A good learning engine asks for the smallest durable change at the right lay1.00
- 141.00
-
- Updating the model weights1.00
- SFT1.00
- imitate correct trajectories; needs labeled examples of the right behavior0.99
- Supervised fine-tuning0.98
- RL post-training1.00
- sample, score against a reward or preference signal, reinforce what wins1.00
- DPO·GRPO·RLVR1.00
- LoRA1.00
- limits the set of parameters that can change; cheaper, safer updates0.99
- Low-Rank Adaptation0.98
- They need: benchmark + evaluator.0.96
- Hard to apply to a raw production log (unless we lift it into a replayable envs0.99
- 151.00
-
- Updating the harness1.00
- Rewrite the prompts, skills, and code around the model.0.99
- Trace-to-harness1.00
- GEPA & prompt search0.99
- A coding agent reads the log + feedback and rewrites1.00
- Mutate prompts, score each candidate, keep the1.00
- a prompt, adds a tool, or patches the workflow.1.00
- winners; evolutionary optimization of the harness.1.00
- Works on (log + feedback) but mostly vibe-based: no0.99
- Testable but needs a benchmark to score against.1.00
- test that the change helped.1.00
- 161.00
-
- Updating the harness1.00
- Rewrite the prompts, skills, and code around the model.0.99
- 小0.87
- Trace-to-harness1.00
- GEPA & prompt search0.99
- A coding agent reads the log + feedback and rewrites1.00
- Mutate prompts, score each candidate, keep the1.00
- a prompt, adds a tool, or patches the workflow.1.00
- winners; evolutionary optimization of the harness.1.00
- Works on (log + feedback) but mostly vibe-based: no0.99
- Testable but needs a benchmark to score against.1.00
- test that the change helped.1.00
- 161.00
-
- Updatingmemory1.00
- Write down facts and distill skills, so the agent doesn't rediscover them.1.00
- Information memory1.00
- store a fact or correction; e.g., "always confirm the date before booking"1.00
- Letta1.00
- ·mem00.90
- Skill distillation0.99
- compress a successful trajectory into a reusable how-to packet0.99
- skills·SKILL.md1.00
- (sometimes viewed as a part of harness)0.99
- Cheapest and fastest; works directly on (log + feedback) but usually unverifie0.99
- 171.00
Transcript
207 cues· 3,120 words· 17,895 chars
- 0:01 Hi, everyone.
- 0:02 My name is Sohail Faizi.
- 0:03 I'm founder and CSO at Relai.
- 0:06 I'm also an associate professor in the computer science department at University of Maryland.
- 0:10 Today, I'm going to talk about continual learning for AI agents, how we can go from failures to durable improvements.
- 0:19 And if you're interested in any of the tools that I'll be talking in this presentation, you can visit at our website, Relai.ai.
- 0:28 Let's get started.
- 0:30 Humans learn mainly from experience by interacting with the world and getting feedback.
- 0:37 The goal of continual learning is to imitate the same for agents so they can also learn from experience by acting, getting feedback and improving without forgetting.
- 0:50 All right, so here's basically a bigger picture of how continual learning for agents look like.
- 0:58 So here is an agent that interact with the world, with diverse users, with complex tools, with various data policies.
- 1:07 And as I mentioned, the goal is to continuously improve the agent from its experience without forgetting.
- 1:12 And this learning can happen in different layers of the agent.
- 1:16 It can happen in the model layer where potentially we can change weights of LLMs or other models used in the agent or use different types of models in the agent.
- 1:27 It can happen in the harness layer where it brings the context
- 1:32 proper context to the LLM with components like prompts, skills, tools, code, workflow.
- 1:39 And it can also happen in the memory, either in session memory or persistent memory of the agent.
- 1:48 But there are two, I would say, fundamental challenges in continual learning for agents.
- 1:53 The first challenge is how to get feedback.
- 1:55 How do we know if the agent did well?
- 1:58 And if not, what should it have done instead?
- 2:01 That's basically the first part, getting the feedback.
- 2:04 And the second part is how we can act upon that feedback, how we can optimize and improve agent and learn from that feedback.
- 2:13 Which layer, which component do we need to change and also how?
- 2:17 I'll be talking about these two challenges, current approaches in order to deal with them and also provide some perspective of how we think about these two problems.
- 2:28 So let's get started with the first problem.
- 2:31 Where does the feedback come from?
- 2:34 So the easy case is when we have a benchmark and some evaluators on that benchmark, so the agent can run tasks from the benchmark.
- 2:43 Now we have the evaluators in order to score, and we can get grades like pass, fail, or reward, as well as potentially some feedback on the agent behavior and agent performance.
- 2:55 This is usually what is happening during the development time that different teams, they curate benchmarks in order to understand the performance of the agent
- 3:03 in certain applications.
- 3:08 But in production, we don't have such benchmark.
- 3:11 We have logs.
- 3:12 Here's an example of a session log where a user is interacting with the agent.
- 3:17 Maybe the user is not very happy with the way the agent is behaving, but we don't have any explicit feedback.
- 3:23 So there are two ways of getting such feedback.
- 3:26 on such session logs.
- 3:29 One is automatic using some other models or LLMs or code in order to analyze the log and provide feedback.
- 3:37 In some cases, even the agent itself can look at it is log and provide some critics of it.
- 3:43 It is automatic and it is scalable.
- 3:47 The second approach is where we have human experts to look at some handful of these logs and provide some domain expert feedback on those agent outputs.
- 3:59 This is lowering the volume, but it is critical because it provides expert knowledge on the behavior of the agent and it is alignment with the way that we want agent to behave in those applications.
- 4:12 Either way, now we have
- 4:14 session log plus some feedback on those logs.
- 4:19 Is it enough?
- 4:21 The answer is no, because it is still not testable.
- 4:25 Here we have log and feedback, but what we really need is a replayable learning environment, a simulation that we can rerun with defined grading on what success looks like, not one instance of what happened and the feedback on top of it.
- 4:43 So what is a learning environment?
- 4:45 Here we are inferring a distribution from one observation that replace what happened and what success means.
- 4:53 The input is what we have, some session logs and feedback.
loading