Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Add configuration option to disable memory/context persistence

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

Bug Description

Memory is opaque to the user. Claude loads itself up with useless context. Especially with Opus 4.7. It saves memories that are only relevant for the task at hand, clogging up future context. I would love a config to completely and entirely disable the feature.

Environment Info

  • Platform: darwin
  • Terminal: tmux
  • Version: 2.1.140
  • Feedback ID: b6d8f70c-f4b6-4e58-af4b-f369a79c6d75

Additional Info

Maybe encourage claude I would love it if claude instead asked the user if it should extend CLAUDE.local.md by the content. If that would then even be monorepo aware (e.g. only add the memory to the package where it is relevant), that would be the icing on the cake and much, MUCH more useful.

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…

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 [Feature Request] Add configuration option to disable memory/context persistence