# mempalace

`mempalace` is an AI memory system — it mines projects and conversations into a
searchable "memory palace" so Claude can recall past decisions and findings
across sessions. It ships 33 MCP tools, auto-save hooks, and guided setup.

It is maintained externally at
[MemPalace/mempalace](https://github.com/MemPalace/mempalace) and **re-listed**
in the `virajp-plugins` marketplace, so it installs from the same place as the
rest. It is also a dependency of `vwf`.

## Install

```sh
pnpx @askviraj/ai-plugins --user mempalace
```

When you install `vwf`, `mempalace` is pulled in and enabled automatically — you
only need this command to install it on its own.

## How vwf uses it

`vwf` uses mempalace as cross-session memory: each cycle recalls prior context
before working and persists durable outcomes after, so detail doesn't pile up in
the conversation. Memory is keyed by your project (the **wing**) and split into
rooms:

| Room        | Holds                                                      |
| ----------- | ---------------------------------------------------------- |
| `decisions` | design/architecture decisions and the *why*                |
| `problems`  | review and security findings, and how they were resolved   |
| `planning`  | plan rationale and deferred options                        |
| `gaps`      | spec/plan holes surfaced during execution, and their fixes |
| `handoff`   | session handoffs for `/vwf:handoff` and `/vwf:recall`      |

Memory is best-effort: if mempalace is unavailable, `vwf` skips every memory
step and proceeds.

## See also

- [../readme.md](../readme.md) — the marketplace overview and full plugin list.
- [vwf guide](../readme.md) — how the Spec → Plan → Execute workflow uses
  memory.
- [MemPalace upstream](https://github.com/MemPalace/mempalace) — full feature
  and tool documentation.