Memory that stays with the project
No Forgetti gives Pi durable, project-scoped memory and reusable project skills. State stays outside the repository, so learning does not create project-file churn.
::: tip New to No Forgetti? Start with Getting started. The default embedded reviewer requires no daemon or service configuration. :::
How it works
The two paths a memory change can take. A direct project_memory write crosses straight to the branch and lands at once. Automatic review takes the long way: it starts only after a turn settles, reads a bounded and sanitized slice of evidence, proposes changes, and commits them only while the branch still matches the version it reviewed. If a newer write got there first, the proposal is refused rather than applied.
The video is silent and animated only in the order things appear, so the paragraph above carries the same information. Project memory covers each step in full.
Choose what you need
| Task | Start here |
|---|---|
| Install the extension and confirm it loaded | Getting started |
| Understand what No Forgetti remembers | Project memory |
| Create and manage reusable workflows | Project skills |
| Let reviews finish after Pi exits | External mode |
| Set up the external worker end to end | External mode setup |
| Diagnose an offline or stalled worker | Operations and troubleshooting |
| Look up a slash command | Command reference |
| Find or remove local state | Storage reference |
The short version
- Scope follows the project. The nearest Git root identifies memory. Without Git, the exact launch directory does.
- Writes are immediate. The
project_memorytool updates canonical project state directly. - Review is conservative. Automatic review runs only after a successfully settled turn and validates changes before admission.
- Skills use Pi’s native path. Active generated skills appear in Pi’s skill index and load progressively when read or invoked.
- External mode is optional. The default
embeddedmode reviews in Pi.externalmode moves accepted review jobs to a separately managed worker.
External mode, in one sentence
Use external mode when memory review must survive Pi shutting down. Pi captures and queues bounded evidence; a user-scoped worker calls the configured reviewer and attempts a compare-and-swap update against current project memory.
External mode does not move foreground memory writes out of Pi, review project skills, or import old sessions. See the complete boundary.