Memory/active plan system is write-only in practice.
Resolved 💬 3 comments Opened Apr 24, 2026 by frankcareccia-oss Closed May 29, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
"Memory/active plan system is write-only in practice. Claude reads the files but doesn't use them to resume work. On
every restart it re-explores the codebase and asks the user to re-explain, defeating the entire purpose of persistent
memory. The startup behavior should be: read plan → check status → resume — not explore from scratch."
What Should Happen?
When Claude restarts actually use the stored files for context not spend time/tokens and user input to regain context
Error Messages/Logs
There are no error messages other than Claude is clueless
Steps to Reproduce
- restart Claude after saving plan and memory
- You have to tell it everything for it to gain context takes a good 10-20 min
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
Claude Code v2.1.94, running on Claude Opus 4.6 (1M context)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗