[Feature Request] Improve memory system conflict resolution and user control over memory behavior

Bug Description
I just want to state that I hate your memory system. It likes to override my memory system, and it's just useless

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.112
• Feedback ID: 7dba7dbb-8081-43db-ad3a-98b7f32ddb01

Errors

[{"error":"MaxFileReadTokenExceededError: File content (34844 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at QyK (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4980:12515)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async dyK (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4984:2638)\n    at async Object.call (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4989:7236)\n    at async UJY (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4439:8320)","timestamp":"2026-04-17T05:21:14.898Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/davidcruwys/dev/clients/supportsignal/app.supportsignal.com.au.\n    at Object.call (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4989:7555)\n    at async UJY (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:4439:8320)","timestamp":"2026-04-17T05:26:28.202Z"}]

Memory in Claude constantly hijacks the fact that I'm sitting in a folder with Claude docs and indexes pointing to all the files I need. And that they are the source of truth or the canonical documents, and then it goes and writes its own random statements which contradict the canonical documents that are really close to it. It's available in the directory if it just looked. It has access to the ClaudeMD where it tells it to look. It has access to the index.md that tells it to look, but it doesn't look. It looks at its own memory system, which keeps failing.