Przejdź do treści
Biblioteka skilli
AI i agenci · Automatyzacja

stateless

/stateless

Sprawdza i wyłącza automatyczną pamięć Claude Code, czyli notatki zapisywane per repozytorium w ~/.claude/projects/PROJECT/memory/, z akcjami status, disable i czyszczeniem pamięci.

Licencja
MIT
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

84/ 100Klasa: dobry
Format9 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
12
Skrypty
4
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 4 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/enumerate-all-projects.sh, scripts/enumerate-all-projects.test.sh, scripts/scope-report.sh, scripts/scope-report.test.sh

Co robi i kiedy

Sprawdza i wyłącza automatyczną pamięć Claude Code, czyli notatki zapisywane per repozytorium w ~/.claude/projects/PROJECT/memory/, z akcjami status, disable i czyszczeniem pamięci.

Wyzwalacze z opisu

make Claude statelessstop Claude rememberingdisable auto memoryturn off auto-memorypurge/clear/delete auto memorywipe what Claude saved about this repodoes Claude have saved memories

Argumenty

/stateless [status|disable|purge]
Oryginalny opis (EN)

Inspect and turn off Claude Code's auto memory, the notes Claude writes itself per repo under ~/.claude/projects/PROJECT/memory/. Use when: 'make Claude stateless', 'stop Claude remembering', 'disable auto memory', 'turn off auto-memory', 'purge/clear/delete auto memory', 'wipe what Claude saved about this repo', 'does Claude have saved memories'. Actions: status (default, memory + settings across all scopes), disable (autoMemoryEnabled:false + CLAUDE_CODE_DISABLE_AUTO_MEMORY), purge (destructive delete, confirm-gated). Auto-memory only, not CLAUDE.md/rules (use /harness-memory:audit) and not

Jak działa

  1. Auto-memory snapshot
  2. Scope
  3. Argument parsing
  4. Precedence
  5. Actions
  6. Boundary, the built-in /memory command
  7. Gotchas
  8. Repo-agnostic contract
Sekcje z nagłówków SKILL.md, w oryginale · 140 linii, 1 169 słów
Podgląd SKILL.md
---
description: "Inspect and turn off Claude Code's auto memory, the notes Claude writes itself per repo under ~/.claude/projects/PROJECT/memory/. Use when: 'make Claude stateless', 'stop Claude remembering', 'disable auto memory', 'turn off auto-memory', 'purge/clear/delete auto memory', 'wipe what Claude saved about this repo', 'does Claude have saved memories'. Actions: status (default, memory + settings across all scopes), disable (autoMemoryEnabled:false + CLAUDE_CODE_DISABLE_AUTO_MEMORY), purge (destructive delete, confirm-gated). Auto-memory only, not CLAUDE.md/rules (use /harness-memory:audit) and not transcripts/history."
argument-hint: "[status|disable|purge]"
user-invocable: true
disable-model-invocation: false
shell: bash
metadata:
  workflow-stage: anytime
  summary: Inspect, disable, or purge Claude Code's per-repo auto memory
---

**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 `/harness-memory:audit`), transcripts, history, or shell snapshots. For the
official full per-project wipe, use `claude purge`.
[reference/official-guidance.md](reference/official-guidance.md), "Out of scope for this skill",
records how this skill treats that command's scope; read the deletion plan and flags at
[Clear local data](https://code.claude.com/docs/en/claude-directory#clear-local-data).

[reference/official-guidance.md](reference/official-guidance.md) holds the decisions this skill
acts on, each with a pointer to its docs section and none of the docs' text; re-read the pointed-at
section before acting on a load-bearing fact.

## 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 `/harness-memory:audit` |
| CLAUDE.local.md | repo only, no user-scope equivalent | No. Use `/harness-memory:audit` |
| Transcripts | `~/.claude/projects/<project>/` | No. How we treat its age sweep and `claude purge`: official-guidance.md, "Out of scope for this skill" |
| Prompt history | `~/.claude/history.jsonl` | No. Same record |
| Session files | `~/.claude/sessions/` | No. Same record |
| Shell snapshots / backups | `~/.claude/shell-snapshots/`, `~/.claude/backups/` | No. Same record |
| Claude Desktop / claude.ai memory | server-side account | Direction only. See [context/desktop.md](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

This skill treats `CLAUDE_CODE_DISABLE_AUTO_MEMORY` as authoritative whenever it is set: `1`
reports auto memory off, and `0` reports it **on** even against `autoMemoryEnabled: false`. Only
when the env var is unset does `autoMemoryEnabled` (by settings precedence) decide. `status` must
report the env var as authoritative whenever it is set. `disable` sets the env var to `1` and
`autoMemoryEnabled: false` together. The reference file's "Precedence: the env var overrides the
setting (VERIFIED)" holds the pointer, as-of date and recheck trigger.

## Actions

- **status** (default): load [context/status.md](context/status.md).
- **disable**: load [context/disable.md](context/disable.md).
- **purge**: load [context/purge.md](context/purge.md).

For the Claude Desktop / claude.ai account store (server-side, not local files), load
[context/desktop.md](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. We never put a `${…}` token in those files: we do not rely
on one being substituted in a file read through the Read tool, or on the Bash tool's environment
carrying `CLAUDE_PLUGIN_ROOT`.

- **Pointer**: for where each `${…}` reference resolves, see
  [Where each variable resolves](https://code.claude.com/docs/en/plugins/manifest-reference#where-each-variable-resolves).
- **As of**: 2026-10-07
- **Recheck trigger**: that table adds supporting files to where a `${…}` reference resolves.

## Boundary, the built-in `/memory` command

"Turn off auto memory" and "what has Claude saved" can land on either.

- **`/memory` (built-in command)**: the person's interactive editor for CLAUDE.md files and the
  auto-memory toggle and entries in the running session. This skill never runs it.
- **This skill (marketplace plugin).** Reports the effective auto-memory state across every
  settings scope and the env var that overrides them, disables it durably through both levers,
  and purges the store behind a manifest and a confirmation gate.

**Routing.** When the person wants a quick interactive toggle or a look at the saved entries,
offer it to the person: you can run `/memory` instead of or alongside this skill. Prefer this skill
when precedence across scopes matters, when the env var is set, or for a durable disable or a
purge. An unattended run records the offer in its output instead of asking.

**Mutation gate.** `/memory` writes whatever the person changes in its dialog; this skill never
runs it on the person's behalf. A `/memory` toggle can be overridden by `CLAUDE_CODE_DISABLE_AUTO_MEMORY`,
which `status` reports.

**Availability is never assumed.** This section states what to do when the person can run
`/memory`, never that it is present in their host. The four-part records live in
[reference/native-memory.md](reference/native-memory.md).

## Gotchas

- **Precedence**: a set `CLAUDE_CODE_DISABLE_AUTO_MEMORY` is authoritative in `status`, `0`
  included. (See above.)
- **`autoMemoryDirectory`**: we treat it as able to relocate the store from *any* scope
  (official-guidance.md, "Storage location"). 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`**: we treat it as relocating the whole config root, the user
  `settings.json` *and* the `projects/<project>/memory/` tree included (official-guidance.md,
  "CLAUDE_CONFIG_DIR relocates the whole config root"). 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**: we treat it as possibly held in the registry rather than a file,
  which `scope-report.sh` can't read. Report managed scope as unread, don't assume empty.
  [Settings scopes and precedence](reference/official-guidance.md#settings-scopes-and-precedence)
  points at where each location is documented (as of 2026-10-11; recheck when that section is
  renamed or moved, or drops its managed-settings location pointer).
- **`disable` leaves this session's loaded memory in place.** What auto memory loaded at startup
  stays in the current context whether or not the setting reloads mid-session, so tell the user a
  new session is the first one that starts without it.
  - **Pointer**: for which settings edits reach a running session, see
    <https://code.claude.com/docs/en/settings#when-edits-take-effect>; for the toggle, see
    <https://code.claude.com/docs/en/settings-reference#automemoryenabled>.
  - **As of**: 2026-10-01
  - **Recheck trigger**: either section changes whether an `autoMemoryEnabled` or `env` edit
    reaches a running 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.
Pliki w paczce (12)
  • SKILL.md 9 KB
  • context/desktop.md 2 KB
  • context/disable.md 6 KB
  • context/purge.md 9 KB
  • context/status.md 5 KB
  • evals/evals.json 5 KB
  • reference/native-memory.md 1 KB
  • reference/official-guidance.md 13 KB
  • scripts/enumerate-all-projects.sh 2 KB
  • scripts/enumerate-all-projects.test.sh 3 KB
  • scripts/scope-report.sh 4 KB
  • scripts/scope-report.test.sh 6 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · melodic-software/claude-code-plugins84MIT
Tyler-R-Kendrick/agent-skills100MIT

Migawka bazy z 13.11.2026 · wersja paczki fa9093c79cd8 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 84audit
    Audytuje warstwę instrukcji i pamięci Claude Code (CLAUDE.md, AGENTS.md, CLAUDE.local.md, .claude/rules/, auto-pamięć) według listy kontrolnej z oficjalnej dokumentacji, z akcjami audit, fix, update i report.
  • 100claude-memory-curator
    Audytuje i bezpiecznie porządkuje instrukcje, reguły, automatyczną pamięć i ustawienia pamięci Claude Code, gdy kontekst jest nieaktualny lub umieszczony w złym miejscu.
  • 100memory-hygiene
    Utrzymuje automatyczną pamięć Claude Code w małym, aktualnym i wiarygodnym stanie: sprzątanie, audyt i aktualizację wpisów MEMORY.md.
  • 100memory-promote
    Audytuje pliki auto-pamięci repozytorium i proponuje przeniesienie każdego do trwalszej warstwy: CLAUDE.md, skilla, hooka w settings.json lub dokumentu referencyjnego.
  • 100auto-memory-pro
    Porządkuje auto-pamięć Claude Code w trwałą wiedzę o projekcie: analizuje MEMORY.md, awansuje sprawdzone wnioski do CLAUDE.md i .claude/rules/ oraz zamienia rozwiązania w skille.
  • 100audit-memories
    Przegląda zapisane pamięci agenta AI: inwentaryzuje je według typu i wieku, wskazuje nieaktualne, sprzeczne lub osierocone i prowadzi przez decyzje o zachowaniu, scaleniu albo usunięciu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.