/toggle-memory — Session Automemory Toggle / Claude Code v2.1.90

What

A new /toggle-memory slash command that disables or re-enables automemory for the current session.

Usage

/toggle-memory

Details

When toggled off: "this conversation will not write or read new memories, and previously-loaded memory content should not be referenced"
When toggled back on: "memory content may be referenced and new memories can be saved"
Memory read/write operations are blocked while toggled off, returning guidance to run /toggle-memory to re-enable
Fires tengu_memory_toggled telemetry with toggled_off boolean
The command is isHidden: false so it appears in command listings, but isEnabled: () => false (the toggle itself is always available; the isEnabled likely gates something else)

Evidence

Toggle-memory command definition (search for "Toggle automemory off/on for this session")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.90

1 Apr 2026 · 16 entries, this one is #3.

Either side of it

Open the release →

Names in this entry

slash/toggle-memory
/pause-memory now shows only in some sessions, and its message says whether memory can be turned back on
flagtengu_memory_toggled
An analytics event, not a feature flag. Claude Code logs it when /pause-memory pauses or resumes memory for the session; the field toggled_off is true when memory was paused.

Is this right?