Arguments. [status|disable|purge]. Default: status

Auto-memory snapshot

bash "${CLAUDE_PLUGIN_ROOT}/skills/stateless/scripts/scope-report.sh" || echo "(snapshot unavailable — run the scope-report script manually)"

Stateless

Inspect and disable Claude Code auto memory, the store Claude writes for itself, one
directory per repo (~/.claude/projects/<project>/memory/, relocatable via
autoMemoryDirectory). Governs auto-memory only. Not in scope: CLAUDE.md / CLAUDE.local.md /
.claude/rules/ (use /claude-memory:audit), transcripts, history, or shell snapshots. For the
official full per-project wipe, use claude project purge. What it does and does not delete is
quoted verbatim in
reference/official-guidance.md; the deletion plan and flags live
in the claude-directory doc.

Criteria and exact doc quotes live in reference/official-guidance.md;
re-fetch the source pages listed there if a fact is load-bearing before you act.

Scope

Entity	Location	This skill
Auto-memory store	~/.claude/projects/<project>/memory/ (or autoMemoryDirectory)	Yes. Status / disable / purge
autoMemoryEnabled setting	any settings scope	Yes. Reads and writes
CLAUDE_CODE_DISABLE_AUTO_MEMORY	OS env or settings env block	Yes. Reads and writes
CLAUDE.md / .claude/rules/	repo + user	No. Use /claude-memory:audit
CLAUDE.local.md	repo only, no user-scope equivalent	No. Use /claude-memory:audit
Transcripts	~/.claude/projects/<project>/	No. Auto-cleaned by cleanupPeriodDays; claude project purge deletes this project's now
Prompt history	~/.claude/history.jsonl	No. Persists indefinitely, not swept by cleanupPeriodDays; claude project purge filters this project's lines
Session files	~/.claude/sessions/	No. One file per running session, cleared when the session exits rather than age-swept; not in claude project purge's deletion list
Shell snapshots / backups	~/.claude/shell-snapshots/, ~/.claude/backups/	No. Swept by cleanupPeriodDays, but not project-scoped, so claude project purge leaves them untouched
Claude Desktop / claude.ai memory	server-side account	Direction only. See context/desktop.md

Argument parsing

Argument	Action
(none) or status	Report the auto-memory posture: effective enabled/disabled state, where the store lives, what it holds. Read-only.
status all	Machine-wide: the status report plus a table of EVERY per-project memory store (scripts/enumerate-all-projects.sh). Read-only.
disable	Turn auto memory off durably (autoMemoryEnabled: false + CLAUDE_CODE_DISABLE_AUTO_MEMORY). Edits settings. Confirm scope first.
purge	Destructive. Delete the auto-memory files. Reads autoMemoryDirectory at every scope first, shows a manifest, offers an opt-in pre-delete backup, and deletes only after explicit confirmation.
purge all	Destructive, machine-wide. Same flow with every per-project store as the candidate set, one combined manifest, and ONE combined gate stating the total count and every directory.

Precedence (documented)

CLAUDE_CODE_DISABLE_AUTO_MEMORY overrides autoMemoryEnabled: per the env-vars doc, =1
disables and =0 forces auto memory on even when autoMemoryEnabled: false would disable
it. When the env var is unset, autoMemoryEnabled (by settings precedence) governs. So a set
env var of 0 alongside autoMemoryEnabled: false means auto memory is effectively on.
status must report the env var as authoritative whenever it is set. disable sets the env
var to 1 (the authoritative lever) and autoMemoryEnabled: false together. See the
reference file's "Precedence: the env var overrides the setting (VERIFIED)".

Actions

• status (default): load context/status.md.
• disable: load context/disable.md.
• purge: load context/purge.md.

For the Claude Desktop / claude.ai account store (server-side, not local files), load
context/desktop.md. Relevant to status and purge whenever the user
wants to be stateless everywhere, not just in this repo.

The context/ files write each bundled script as <skill-dir>/scripts/<name>.sh, where
<skill-dir> is this skill's directory: ${CLAUDE_SKILL_DIR}. Put that path in place of the
placeholder before running a command; a file read through the Read tool is not substituted, and
the Bash tool's environment has no CLAUDE_PLUGIN_ROOT. Basis: the plugins reference, "Where each
variable resolves", verified 2026-09-27; recheck when that table adds supporting files.

Gotchas

• Precedence: CLAUDE_CODE_DISABLE_AUTO_MEMORY overrides autoMemoryEnabled (=0 forces
  on even against autoMemoryEnabled: false). A set env var is authoritative in status. (See above.)
• autoMemoryDirectory relocates the store and is read from any scope. The snapshot
  prints the slug-derived default only. purge and status must read the override at every
  scope or they act on the wrong directory.
• CLAUDE_CONFIG_DIR relocates the whole config root: when set, the user settings.json
  and the projects/<project>/memory/ tree live under it, not ~/.claude. All scope and
  memory-dir resolution honors ${CLAUDE_CONFIG_DIR:-~/.claude} (scripts + workflows); the
  snapshot reports the resolved root, and purge's relocation check treats it as expected.
• Windows managed policy can live in the registry (HKLM/HKCU\SOFTWARE\Policies\ClaudeCode),
  not a file. scope-report.sh can't read it. Report managed scope as unread, don't assume empty.
• disable applies next session, not immediately: the setting and env block are read at
  startup. Tell the user to restart / start a new session.
• Tracked settings.json: a live edit to a dotfile-manager-tracked settings file must be
  backfilled to the source; never run an apply that could revert the edit.
• Desktop / claude.ai memory is server-side. purge cannot delete it; give direction only.

Repo-agnostic contract

Discover the consumer's state at runtime. Never hardcode a machine's paths or current
posture. Settings scopes, the memory directory, and the env var are read fresh from the
snapshot above and the workflow scripts. The bundled scope-report.sh reuses the plugin's
single-source memory-dir resolver (skills/audit/scripts/resolve-memory-dir.sh) rather than
re-implementing slug derivation.