claude-code - 💡(How to fix) Fix Memory and instructions not effectively followed across sessions - repeated mistakes waste tokens and user time

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Problem

I'm a paying subscriber using Claude Code with multi-agent workflow (Claude + Gemini MCP). Despite having extensive memory files, CLAUDE.md rules, and feedback records, Claude repeatedly fails to follow its own recorded instructions, resulting in:

  1. Same mistakes repeated every session - I have to re-remind Claude of rules that are already written in memory files. What's the point of the memory system if it doesn't actually change behavior?

  2. Massive token waste on verification loops - Simple checks (e.g., "is this binary installed?") turn into 5+ failed attempts instead of using the right tool from the first try. This burns through credits for zero value.

  3. Declaring work "complete" without actual verification - In my case, Claude added a blender-mcp config that requires uvx, but never checked if uvx was installed. Reported "setup complete, just restart." After restart, nothing works. I had to debug it myself.

  4. Ignoring cross-check workflow - My team rules require Claude to cross-check with Gemini before reporting. Claude skips this and makes solo judgments that turn out wrong.

  5. Cost vs value - I'm paying for max effort level, using Opus, and getting results that require me to manually verify and re-instruct every single time. The token consumption is high but the actual delivered value doesn't match.

Expected behavior

  • Memory records and CLAUDE.md instructions should meaningfully constrain behavior, not just exist as files
  • Environment/setup tasks should include actual execution verification before reporting completion
  • When team workflow rules say "cross-check with another agent", that should actually happen

Environment

  • Claude Code on Windows 11
  • Claude Opus 4.6 (1M context)
  • Multi-agent setup (Claude + Gemini MCP bridge)
  • Extensive memory system with 20+ recorded feedback/rules

Impact

Considering canceling subscription. The cost of re-instructing and verifying Claude's work every session approaches the cost of just doing the work myself.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • Memory records and CLAUDE.md instructions should meaningfully constrain behavior, not just exist as files
  • Environment/setup tasks should include actual execution verification before reporting completion
  • When team workflow rules say "cross-check with another agent", that should actually happen

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Memory and instructions not effectively followed across sessions - repeated mistakes waste tokens and user time