Every new session, your agent forgets what it already learned

Persist what the agent learns and load it at session start, and each run builds on the last. Start cold every time and the agent re-derives, re-asks, and repeats yesterday's mistakes.

B

Balagei G Nagarajan

3 MIN READ


An agent starting each session with no memory, repeating prior work and errors

Key facts.

  • SimpleQA shows even strong models frequently fail simple, verifiable questions, so an agent that re-derives facts from scratch each session repeats avoidable errors. source
  • FaithfulRAG shows models override retrieved context with parametric knowledge, so even reloaded memory can be ignored unless the agent is built to honor it. source
  • A cold-start agent re-derives facts each session and a bigger model still fails SimpleQA, so it repeats the rework just as wrong. (arXiv:2506.08938)
Durable memory loaded at start is what survives those boundaries, not an always-on process.
— from "Every new session, your agent forgets what it already learned"

Why does cold start hurt so much?

An agent with no persistent memory treats every session as the first. It re-derives facts it established yesterday, re-asks questions a user already answered and re-makes mistakes someone already corrected, because the correction lived only in a conversation that ended. For a one-off task that is merely wasteful; for an agent meant to handle recurring work, it is corrosive, because the agent never accumulates the competence that comes from experience. The SimpleQA result sharpens the risk: models fail even simple verifiable questions, so an agent re-deriving from scratch is not just slow, it is re-rolling the dice on errors that a remembered answer would have avoided.

The fix is to give the agent durable memory: persist the corrections, the resolved facts, the user preferences and load them at session start so each run begins where the last left off. But restoring memory is only half the job. FaithfulRAG shows models will sometimes ignore the context they are handed and answer from their training instead, so a reloaded memory the agent overrides is no better than no memory at all. The agent has to be built to actually honor its persisted knowledge, treating a remembered correction as authoritative rather than as a suggestion it can overrule with a confident guess.

A warm-start flow loading persisted memory at session start versus a cold start re-deriving everything

What does warm start require?

ElementCold startWarm start
Prior correctionsForgottenPersisted and loaded
Resolved factsRe-derivedReused
Honoring memoryN/ATreated as authoritative
Each sessionStarts from zeroBuilds on the last

Persisting the right memory and getting the agent to honor it means knowing which learned facts matter for a given situation, which the Pattern Intelligence Layer makes explicit. VibeModel ties remembered corrections to the patterns they apply to, so the agent loads and respects the knowledge relevant to what it is doing, turning each session into a step forward instead of a restart from cold.

Frequently asked questions

Why not just keep the agent running?
Sessions end, processes restart and context windows fill. Durable memory loaded at start is what survives those boundaries, not an always-on process.

Is reloading context enough?
No. FaithfulRAG shows models can ignore provided context and answer from training. The agent must be built to treat persisted corrections as authoritative.

What should persist?
Corrections, resolved facts and user preferences, the things that let the next session build on the last instead of re-deriving them and risking fresh errors.


Share this post

Join the discussion

Have a take, a war story, or a question? Sign in with GitHub to comment and react. Comments are powered by GitHub Discussions, ad-free and yours to moderate.

Continue Reading

Find where your agent breaks, before you build it

Faultmap maps where your agent will fail from the goal and your data, then hands you the first test suite it has to pass.