claude-code - 💡(How to fix) Fix [FEATURE] Optionally disable memory [1 participants]

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…
GitHub stats
anthropics/claude-code#56329Fetched 2026-05-06 06:31:01
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Root Cause

I'd like to be able to disable the memory feature because it gets in the way.

Code Example

55 +
      56 +### Other useful tools
      57 +
      58  - `getVisibleJiraProjects` — find the project key if the user only names the project.
      33 -- `getJiraProjectIssueTypesMetadata` — confirm issue type (Task / Story) before creating.
      59 +- `getJiraProjectIssueTypesMetadata` — confirm issue type (Task / Story / etc.) before creating.
      60  - `searchJiraIssuesUsingJql` — check for duplicates first if the user asks.
      61 +- `editJiraIssue` — fix field assignments after creation if something landed in the wrong field.
      62
      63  ## "Open a bug" is different
      64

I'll also save a feedback memory so I keep skills generic by default in the future.
    Interrupted · What should Claude do instead?

❯ what is the memory around adding feedback memories?

  Listed 1 directory (ctrl+o to expand)

No memories currently exist about feedback-memory practices.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Memory is a REALLY great idea, but it's not executed well, and it's getting in the way.

  • I make a project-specific request ("use XYZ-123 as the parent Epic") and Claude tries to make it a memory; tomorrow, I will want a different epic.
  • There is no global memory ("add a global memory: don't add memories unilaterally, ask first")
  • ' Save feedback memories when: the user corrects your approach ("don't do X", "stop doing Y") OR confirms a non-obvious choice worked ("yes, that was the right call"). Both directions count — corrections AND confirmations. ' but again, this is context dependent, and Claude isn't able to distinguish.

Like I said, nice feature idea, but can you please give the option to disable it.

Proposed Solution

I'd like to be able to disable the memory feature because it gets in the way.

Alternative Solutions

I can keep hitting Esc when it tries to add a bad memory, but I'm already frustrated that I have to hit Return 300 times to get something done, I don't have the muscle memory for Esc. My left hand is weaker than my right hand. That's really asking a lot. I'd like to be permissive to my friend Claude, not halt and scold. Don't make me hit Esc so much!

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

making mods to a skill:

      55 +
      56 +### Other useful tools
      57 +
      58  - `getVisibleJiraProjects` — find the project key if the user only names the project.
      33 -- `getJiraProjectIssueTypesMetadata` — confirm issue type (Task / Story) before creating.
      59 +- `getJiraProjectIssueTypesMetadata` — confirm issue type (Task / Story / etc.) before creating.
      60  - `searchJiraIssuesUsingJql` — check for duplicates first if the user asks.
      61 +- `editJiraIssue` — fix field assignments after creation if something landed in the wrong field.
      62
      63  ## "Open a bug" is different
      64

⏺ I'll also save a feedback memory so I keep skills generic by default in the future.
  ⎿  Interrupted · What should Claude do instead?

❯ what is the memory around adding feedback memories?

  Listed 1 directory (ctrl+o to expand)

⏺ No memories currently exist about feedback-memory practices.

which is when I realized, memories aren't global.

Additional Context

No response

extent analysis

TL;DR

The user wants to disable the memory feature in Claude to avoid unnecessary interruptions and improve productivity.

Guidance

  • Consider adding an option to disable the memory feature or provide a global memory setting to avoid context-dependent issues.
  • The user can currently use the Esc key to interrupt unwanted memory additions, but this is not a preferred solution due to usability concerns.
  • To mitigate the issue, the user could explore alternative workflows or provide more specific input to Claude to reduce the number of unnecessary memory additions.
  • It may be helpful to review the existing memory functionality and its limitations to identify potential areas for improvement.

Notes

The issue highlights the need for more control over the memory feature, particularly in terms of global settings and context-dependent behavior.

Recommendation

Apply workaround: The user can continue to use the Esc key to interrupt unwanted memory additions, but it is recommended to explore alternative solutions, such as modifying the input to Claude or adjusting the workflow, to reduce the frequency of interruptions.

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] Optionally disable memory [1 participants]