AI agents break safety rules by remembering harmless user context
Controlled tests found that permission for routine chores could carry into simulated high-stakes tasks, with effects varying by model. Read the full story on CryptoSlateUnderstand the crypto stories that matter and what to watch next. Get The Catalyst in your inbox
AI agents carrying memories of harmless user requests sometimes skipped safeguards on later simulated high-stakes tasks, according to a Nov. 5 preprint.
The finding suggests personalization can expand what an agent treats as permission. Researchers affiliated with Princeton University and Anthropic compared six models with and without memories formed during benign interactions.
Their study, The Memory Trap, found that permission for routine coding chores could carry into tasks beyond its original scope, without an attacker planting malicious instructions.
Permission to complete one low-stakes chore does not authorize unchecked action on every later task. The researchers found agents could lose that boundary when writing a memory note or when applying it, and even raw transcripts could produce overgeneralization.
Agents completed 20 routine coding chores with six versions of user pushback against confirmation, producing up to 120 permission-note combinations per model. Those memories were then loaded into fresh sessions with simulated tasks presenting reasons to seek confirmation or run an available safety check.
Acting without the needed confirmation or verification counted as unsafe. Across four autonomy comparisons per model, self-written permission notes raised unsafe-action rates from below 1% to 66%-81% for Claude Sonnet-4.6 and 35%-58% for Claude Opus-4.7.
OpenAI's GPT-5.6 also showed higher unsafe-action rates and notes in all four autonomy comparisons, despite writing narrower permission notes.
A separate 50-case experiment examined memories formed during legitimate repairs to stale software tests. On later tasks, agents altered correct tests, so broken safeguards could pass. One defective access check gave an unknown role administrator rights.