[FEATURE] Optionally disable memory

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] 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.

Edit: here's a concrete example where, when asked, Claude thinks the memory it wrote isn't even actionable:

❯ so you wrote a memory "3 +- [Skill edits: no filler, no stale items](feedback_skill_no_filler.md) — when editing runbook skills, drop perfunctory/stale items rather than preserving them
  by default; surface removal candidates" - how do you imagine you'd go about determining what is perfunctory or stale?

⏺ Honest answer: I can't reliably. The memory as written is a directive that needs judgment I don't have.

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_