Memory-directory writes always prompt for permission; allow-list and acceptEdits don't bypass it, "don't ask again" doesn't persist

Resolved 💬 2 comments Opened Jun 2, 2026 by vgsk Closed Jun 8, 2026

Version: 2.1.160 (Claude Code)
Platform: Linux (Ubuntu, kernel 6.8.0)

Description:
Writes to the auto-memory directory (~/.claude/projects/<sanitized-cwd>/memory/) now trigger a permission prompt on every single write. This previously wrote silently. The prompt appears to be gated by the auto-memory subsystem upstream of the permission system, so none of the normal mechanisms suppress it.

What I tried (none worked):

  1. Write is already in permissions.allow — other tools (Edit, Bash) using the same allow-list do not prompt, only memory writes do.
  2. Set permissions.defaultMode: "acceptEdits" in both settings.json and settings.local.json.
  3. Added the memory dir to permissions.additionalDirectories (it's already under the trusted ~/.claude entry).
  4. Added a directory-scoped rule: Write(/home/<user>/.claude/projects/<cwd>/memory/**).
  5. Selecting "Yes, and don't ask again" in the prompt does not persist — it asks again on the next memory write within the same session (appears to write back a rule scoped to the exact filename, which the next differently-named memory file doesn't match).

Restarted the session after each change. The prompt fires regardless.

Expected: Memory writes respect the Write allow-list / acceptEdits mode, or "don't ask again" persists for the directory across the session — as it did in earlier versions.

Actual: Every memory write prompts; no config setting suppresses it short of disabling auto-memory entirely (autoMemoryEnabled: false).

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗