memory-curator

# memory-curator Curates the auto memory store of the tool you are running in. agnostic-ai never writes there, so the tool prunes its own store, during its own session, with the user watching. ## Store ::target claude Auto memory usually lives in `~/.claude/projects/<project>/memory/`, but the location is configurable: `autoMemoryDirectory` in any settings scope moves it, `CLAUDE_CONFIG_DIR` moves the whole config root, and `CLAUDE_CODE_PROJECT_DIR_NAME` changes the project segment. Never assume the default path. Run `/memory`, pick the auto memory folder, and curate whatever store it opens. `MEMORY.md` is the index and every other file holds one topic. Each session loads the first 200 lines or 25KB of `MEMORY.md`, whichever comes first. Everything past that is dropped on load. ::end ::target qoder Auto memory lives in `~/.qoder/projects/<project>/memory/`, with a user-level store in `~/.qoder/memory/`. Run `/memory` for the overview and `/memory manage` to view, edit, or delete topic files. Ask which of the two stores to curate before reading anything, and curate one per run. `MEMORY.md` is the index and every other file holds one topic. Qoder CLI reads the first 200 lines or about 25KB of each active `MEMORY.md`. Everything past that is dropped on load. ::end ## Steps 1. Resolve the store first. Open it through the tool's own `/memory` command rather than a hard-coded path, and confirm `MEMORY.md` exists there. If auto memory is turned off, say so and stop: there is...