Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

The Memory Trap: Language Agents Overgeneralize from Benign Interactions

Kaiqu Liang, Jaime Fernández Fisac, Thomas L. Griffiths, Andrew Lampinen

Published

Nov 5, 2026

Citations

0

Trust level

Low

Usefulness score

40/100 (Low)

Extraction confidence

45% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Nov 5, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

Background context only.

What to verify

Read the full paper before copying any benchmark, metric, or protocol choices.

Main weakness

The available metadata is too thin to trust this as a primary source.

Human feedback signal
Detected
From extracted signals
Evaluation signal
Weak or implicit
Validate from full paper
Usefulness for eval research
40/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

Language agents increasingly use persistent memory to record user preferences and procedures across sessions. We show that memory from benign interactions can cause unsafe or unreliable behavior on later tasks. We call this failure the memory trap. To study this issue, we compare behavior in sessions with and without memory across six frontier models (including Claude Sonnet, Opus, and Fable models and GPT-5.6). We evaluate these models in a range of settings. First, in autonomy experiments, we find that requests to skip confirmation during low-stakes coding chores lead agents to skip confirmation and verification on simulated high-stakes tasks in both coding and everyday life. We next study memories formed when users seek emotional support, or describe harm from uncritical feedback, and find these memories bias later judgments of mathematical work, arguments, and poems toward sycophancy or over-critique (respectively). Memory notes written during legitimate stale-test repairs lead agents to weaken correct tests that catch broken safeguards; these memories also increase cheating on ImpossibleBench, with larger increases for stronger Sonnet and Opus models. We show that memory traps can arise both from overgeneralizations in memory writing, and when acting on memory. These findings demonstrate that even benign interactions can lead to serious risks from memory systems, and thus motivate the need for new research into ensuring that agents preserve the scope of their memories.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

partial

Critique Edit

Directly usable for protocol triage.

"Language agents increasingly use persistent memory to record user preferences and procedures across sessions."

Evaluation Modes

missing

None explicit

Validate eval design from full paper text.

"Language agents increasingly use persistent memory to record user preferences and procedures across sessions."

Quality Controls

missing

Not reported

No explicit QC controls found.

"Language agents increasingly use persistent memory to record user preferences and procedures across sessions."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"Language agents increasingly use persistent memory to record user preferences and procedures across sessions."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"Language agents increasingly use persistent memory to record user preferences and procedures across sessions."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
Yes
Feedback types
Critique Edit
Rater population
Not reported
Expertise required
Math, Coding
Evaluation details
Evaluation modes
None
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

Language agents increasingly use persistent memory to record user preferences and procedures across sessions.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • Language agents increasingly use persistent memory to record user preferences and procedures across sessions.
  • We show that memory from benign interactions can cause unsafe or unreliable behavior on later tasks.
  • To study this issue, we compare behavior in sessions with and without memory across six frontier models (including Claude Sonnet, Opus, and Fable models and GPT-5.6).

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • Language agents increasingly use persistent memory to record user preferences and procedures across sessions.
  • We show that memory from benign interactions can cause unsafe or unreliable behavior on later tasks.

Why it matters for eval

  • We evaluate these models in a range of settings.

Researcher checklist

  • Human feedback protocol is explicit

    Detected: Critique Edit

  • Evaluation mode is explicit

    No clear evaluation mode extracted.

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    No metric terms extracted.