Memory save requests ignored — session context lost, tokens wasted

Resolved 💬 1 comment Opened Apr 23, 2026 by 6ora Closed May 27, 2026

Preflight Checklist

  • [x] I have searched existing issues for similar behavior reports
  • [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

I explicitly asked Claude to save memory mid-session. Multiple times. It said "I'll save it" and did absolutely
nothing. Then context compression hit, wiped everything, and the next session had zero memory of prior work.

Rinse and repeat. Every. Single. Session.

What Claude Actually Did

What Actually Happened:
Memory writes were deferred or silently skipped. Context compression fired first. Hours of session context —
gone. Had to re-explain everything from scratch, burning a significant chunk of tokens in the process.

At this point I'm genuinely wondering if the token waste is a feature, not a bug.

Expected Behavior

Expected Behavior:
When a user says "save this" — save it. Immediately. Not after finishing the current task. Not eventually. Now.

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

_No response_

Claude Model

Sonnet

Relevant Conversation

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.118

Platform

Anthropic API

Additional Context

Environment:

  • Claude Code, Windows 11
  • Model: claude-sonnet-4-6
  • Sessions: multiple, same issue every time

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗