Teaching Agents to Forget: Why It’s Harder Than Remembering

The inverted question

The industry races to extend context windows and persistent memory. A research line asks the opposite:

When an autonomous agent cannot keep everything, what should it forget so later tasks don’t slowly drift off course?

Monday 9:07 a.m.

Customer support ticket #38 pops up. An agent inherits all overnight context — policies, temp fixes, angry threads, half-applied refunds. If it remembers literally everything, it may:

• Over-weight obsolete instructions
• Repeat revoked compensations
• Confuse user personas across sessions Forgetting is a feature, not a bug — but curated forgetting.

Why forgetting is harder

Remember	Forget
Append to log	Judge salience + liability
Benchmark: recall@k	Benchmark: task success after N steps
Product story: “never lose context”	Requires governance (what must persist for compliance?)

Design implications

1. Tiered memory — working / episodic / institutional
2. Decay policies tied to task type, not arbitrary token limits
3. Human-visible summaries before purge events
4. Evaluation suites for long-horizon drift, not single-turn accuracy

FAQ

Q1: Won’t big contexts solve this? A: Cost, latency, and attention dilution still punish “keep it all” at production scale. Q2: Link to Agent Economy? A: Portable memory only works if forgetting rules are portable too — otherwise agents become liability suitcases.

Research note · Dr.Jingle · Not technical endorsement of any paper.