pi-memoria 0.1.3 → 0.2.0

package/README.md

@@ -1,367 +1,115 @@
 # pi-memoria
 
-Agent-first long-term memory for [pi](https://github.com/badlogic/pi-mono).
-
-memoria gives a coding agent a memory it can actually rely on: a plain-markdown
-library on disk, a prose briefing that is loaded into every session, and
-automatic recall that searches the whole library on every prompt — in well under
-a millisecond.
-
-- **Nothing is lost behind an API.** Every memory is a markdown file you can
-  read, edit, grep, diff and version.
-- **Past conversations are searchable too.** When the library has nothing, the
-  agent can search the raw transcripts of earlier sessions before saying it does
-  not remember.
-- **Recall is automatic.** Relevant notes are injected before the model answers,
-  so it does not have to remember to ask.
-- **Broad topics, never fact files.** `likes-apples.md` is a defect; facts
-  accumulate in `food-preferences.md`.
-- **Names are handles.** Aliases make every nickname, full name or former name
-  resolve to the same note. Re-filing or consolidating notes also keeps retired
-  note ids usable as references.
-- **Zero runtime dependencies.** No database, no server, no embedding service, no
-  build step. Retrieval is a BM25 index kept in memory.
+Long-term memory for [pi](https://pi.dev). Saves preferences, project context and
+past decisions as Markdown files, then retrieves relevant notes in later sessions.
 
-```
-┌──────────────────────────────────────────────────────────────┐
-│ layer 1  MEMORY.md        always in the system prompt         │
-│ layer 2  auto-recall      best matches injected per prompt    │
-│ layer 3  memoria_recall   the agent can search deeper         │
-│ layer 4  plain markdown   read/grep the files directly        │
-└──────────────────────────────────────────────────────────────┘
-```
-
-Measured on the bundled corpus: **recall@5 = 100%, recall@1 = 92.5%** over 40
-questions (paraphrases, typos, aliases, CJK, identifiers, superseded notes) with
-an average query time of **0.16 ms** (`npm run eval`).
-
-## Contents
-
-- [Install](#install)
-- [Quick start](#quick-start)
-- [How it works](#how-it-works)
-- [The memory library](#the-memory-library)
-- [Tools](#tools)
-- [Commands](#commands)
-- [Configuration](#configuration)
-- [Scopes: personal, project, read-only](#scopes-personal-project-read-only)
-- [Synonyms](#synonyms)
-- [Model reranking](#model-reranking)
-- [Automatic session learning](#automatic-session-learning)
-- [Session recall](#session-recall-past-conversations)
-- [Backup and migration](#backup-and-migration)
-- [Performance](#performance)
-- [Privacy and durability](#privacy-and-durability)
-- [Troubleshooting](#troubleshooting)
-- [Development](#development)
-- [Design notes and limits](#design-notes-and-limits)
-- [License](#license)
+Memory lives in your agent directory and follows you across projects. Search runs
+locally, with no database, embedding service or additional runtime dependencies.
+The agent can also search pi's saved conversations when a detail was never saved
+as a note.
 
 ## Install
 
-### Copy it into the extensions directory (simplest)
+Requires pi and Node.js **22.19.0 or later**.
 
-```bash
-mkdir -p ~/.pi/agent/extensions/memoria
-cp index.ts package.json ~/.pi/agent/extensions/memoria/
-cp -r src skills ~/.pi/agent/extensions/memoria/
+```sh
+pi install npm:pi-memoria
 ```
 
-Pi discovers `extensions/memoria/index.ts` on the next start (or after
-`/reload`). Three notes:
-
-- **Do not copy `node_modules/`.** Pi supplies `typebox` and the
-  `@earendil-works/pi-*` packages to extensions, so the copy works with no
-  dependencies installed.
-- `package.json` is optional for this route; it carries the `pi.extensions` and
-  `pi.skills` manifest and the peer-dependency metadata used by the package
-  route.
-- The bundled skill is discovered automatically when memoria is installed as a
-  **package** (`pi install …`). For the copy route, copy it separately if you
-  want it: `mkdir -p ~/.pi/agent/skills && cp -r skills/memoria ~/.pi/agent/skills/`.
-
-### Install as a pi package
-
-```bash
-pi install git:github.com/rcsaquino/pi-memoria@v0.1.3
-pi install npm:pi-memoria                 # if published to npm
-pi install ./path/to/pi-memoria           # or from a local checkout
-pi list
-pi remove git:github.com/rcsaquino/pi-memoria@v0.1.3
-```
-
-`pi install` records the package in `~/.pi/agent/settings.json` (or
-`.pi/settings.json` with `-l`, which loads only after project trust) and clones
-the repository to `~/.pi/agent/git/<host>/<owner>/<repo>`. It runs
-`npm install --omit=dev` in the clone; this package declares the pi-provided
-modules as *optional* peers so npm does not fetch a second, ~450 MB copy of pi.
-The installed package is around 700 KB with no `node_modules`.
-
-The package also ships a skill (`skills/memoria/SKILL.md`) that teaches an agent
-how to maintain the library — where a fact belongs, how to consolidate notes, and
-what never to do.
+Restart pi or run `/reload` to load the extension and its bundled skills.
+No configuration is required.
 
-### Try it without installing
+Alternatively, install a tagged release from GitHub:
 
-```bash
-pi --extension /path/to/memoria/index.ts
-# from a checkout:
-pi -e ./index.ts
+```sh
+pi install git:github.com/rcsaquino/pi-memoria@v0.2.0
 ```
 
-## Quick start
-
-Nothing to configure. In a session:
+Use one installation method, not both.
 
-```
-You:  Remember that I take my coffee with oat milk and I'm lactose intolerant.
-Agent: [memoria_write { topic: "Dietary preferences", category: "preferences" }]
+## Use it
 
-... days later, in a different project ...
+Ask pi to remember something:
 
-You:  Order me a flat white.
-Agent: [auto-recall surfaces "Dietary preferences — drinks oat milk; lactose intolerant"]
+```text
+Remember that I use pnpm for personal projects and prefer tabs over spaces.
 ```
 
-Other things you can say or run:
+In a later session, relevant notes are added to the agent's context automatically.
+You can also ask directly:
 
-```bash
-/memoria status            # where the store is and how healthy it is
-/memoria store remember to renew the Datadog contract in August
-/memoria search datadog contract
-/memoria topics            # review notes: facts, size, usage, merge candidates
-/memoria doctor            # consistency problems and housekeeping hints
-/memoria learn             # extract durable facts from this session
+```text
+What package manager do I use for personal projects?
+What did we decide about the deployment last week?
 ```
 
-## How it works
-
-1. **`MEMORY.md`** lives in the store root and is injected into the system
-   prompt on every model call, capped at `hotLimit` (5000 characters). It is a
-   short **prose** briefing — who the user is, how they work, hard constraints,
-   the state of active work — not a log: no headings, no bullets, no
-   annotations. Being stable, it does not invalidate the prompt cache.
-2. **Auto-recall** searches the library on every user prompt and injects the
-   best matches as a `memoria_recall` message, with ids, paths and excerpts. The
-   previous turn is folded in at a lower weight (`autoRecallPriorWeight`) so a
-   long earlier message cannot out-vote the current question.
-3. **`memoria_recall`** lets the agent search deeper, with filters for category,
-   tags, priority, recency, scope and score, plus an optional scoring breakdown.
-4. **Plain markdown**: `library/INDEX.md` and per-category indexes provide a
-   generated table of contents, and `read`/`grep`/`cat` work on the files.
-5. **Past conversations**: if the library has nothing, the transcripts pi saved
-   for earlier sessions are searched as a last resort, with file-and-line
-   citations so anything found can be verified in context.
-
-Ranking combines BM25 over weighted fields (title, tags, aliases, links,
-summary, category, body) with boosts for exact phrases, priority, recency, query
-coverage, time windows ("last week"), related notes, and a demotion for notes
-that a newer note declares superseded. Matching is resilient: identifiers and
-paths match literally, plurals and verb forms match through a conservative
-stemmer, `kuber` finds `kubernetes`, one or two typos still hit, and CJK text is
-matched with unigrams and bigrams.
-
-## The memory library
+Useful commands:
 
-```
-<agent dir>/memoria/
-├── MEMORY.md                          always-injected prose briefing
-├── config.json                        optional store configuration
-├── synonyms.json                      optional query-side synonym table
-├── library/
-│   ├── INDEX.md                       generated table of contents
-│   ├── people/<topic>.md              one note per broad topic
-│   ├── projects/<topic>.md
-│   ├── preferences/<topic>.md
-│   ├── decisions/<topic>.md
-│   ├── workflows/<topic>.md
-│   ├── knowledge/<topic>.md
-│   └── inbox/<topic>.md               quick captures, triaged later
-├── .index/                            derived: index.json|index.bin, usage.json
-└── .trash/                            soft-deleted notes
-```
+| Command | Purpose |
+| --- | --- |
+| `/memoria` | Show store status and the briefing's size |
+| `/memoria search <query>` | Search saved notes |
+| `/memoria sessions <query>` | Search earlier conversations |
+| `/memoria topics` | Review notes and possible duplicates |
+| `/memoria doctor` | Check for consistency problems |
+| `/memoria paths` | Show storage locations |
 
-`<agent dir>` is `~/.pi/agent` by default, or `$PI_CODING_AGENT_DIR` when pi's
-agent directory is customized. Because the store is user-level, memories follow
-you across projects: remember something in one repository and recall it in
-another.
-
-Pi's own conversation transcripts live next to the store at
-`<agent dir>/sessions/` (plus `sessions-archive/` if you keep one). They are read
-by [session recall](#session-recall-past-conversations) and never modified.
-
-### Broad topics, never facts
-
-| User says | Stored as | Not as |
-|---|---|---|
-| "I like apples" | `library/preferences/food-preferences.md` → `- **Fruit** — Likes apples.` | `likes-apples.md` |
-| "I like pears" | appended to the same `food-preferences.md` | `likes-pears.md` |
-| "Alice prefers oat milk" | `library/people/alice.md` | `alice-prefers-oat-milk.md` |
-| "my dad is Bob" | `library/people/bob.md` → `- **Bob** — John's father, retired.` | `dad.md`, `johns-father.md` |
-
-Rules enforced by the store, not merely requested from the model:
-
-- The file name is always `slugify(topic)`. Topics that read like a single fact
-  (`likes apples`, `I like apples`) or like a **relationship** (`John's father`,
-  `dad`, `Alice's manager`) are rejected and the fact is filed under the category
-  name instead (`people.md`), with an explanatory note returned to the agent.
-  A relationship goes in the fact text; the note is named after the subject.
-- Writing to an existing topic **appends** under a `## Facts` section, skipping
-  duplicates. There is no one-file-per-fact path.
-- A note may grow to `topicMaxChars` (default 8000) before new facts spill into
-  `topic-2.md`.
-- `memoria_write` accepts `mode: "new"` to force a sibling file and
-  `mode: "replace"` to overwrite a note deliberately.
-- `memoria doctor` flags any file named after a fact or a relationship.
-
-### Names change: aliases first, renames second
-
-A person is not their name, and the first name you learn is rarely the one you
-keep. Notes therefore carry **aliases** in frontmatter, indexed at tag weight:
-
-```markdown
----
-topic: Bob
-aliases: ["Robert", "Bobby", "John's father"]
----
-```
+Saving a fact and retrieving it are separate steps. Automatic recall searches
+existing notes; it does not turn every conversation into a memory. The agent
+saves a note when something is worth keeping.
 
-Any of `Bob`, `Robert`, `Bobby`, `John's father` — and the file name — recalls
-the note, so retrieval never depends on which name won the file name.
+## What gets remembered
 
-When the better name *is* known, `memoria_move` re-files the note:
+Memoria keeps three sources of context:
 
-- Target free → the file is **renamed**; the note keeps its `id`, so ids read
-  earlier in the session stay valid.
-- Target exists → the move reports a conflict. Set `merge: true` to combine the
-  facts and links (duplicates skipped, nothing overwritten) and move the old
-  file to `.trash/`. A merge refuses to discard aliases or links when their
-  limits are full.
-- The previous topic, title and file name are added to the target's aliases, so
-  old references keep working.
+- **A short briefing** (`MEMORY.md`): standing preferences and context included
+  in the system prompt. Limited to 5,000 characters by default.
+- **Topic notes** (`library/`): people, projects, decisions and other details
+  retrieved when relevant. Facts about the same subject accumulate in one file.
+- **Saved conversations**: read-only searches of pi's transcripts, with file and
+  line references so the agent can check the surrounding dialogue.
 
-Renaming is deliberately an explicit agent action rather than a side effect of
-writing: renaming during an unrelated write is how you end up with `bob-2.md`
-and a path the agent read earlier in the session that no longer exists.
+For example, several preferences belong in `preferences/dietary-preferences.md`,
+not separate `likes-apples.md` and `likes-pears.md` files. Notes support aliases,
+links and superseded decisions. Renaming a note preserves its identity; merging
+notes requires an explicit request.
 
-### Related notes and superseded notes
+The default store is separate from the installed extension:
 
-```markdown
----
-related: ["mem_1758_ab12"]          # pulled into recall with the source note
-supersedes: ["Deploy process"]      # this note replaces that one
----
-```
-
-- `related` notes are appended to recall results (`related` marker) and shown by
-  `memoria_read`, so following a reference works from either end.
-- A note that another note declares `supersedes` stays searchable but is
-  **demoted and flagged** (`SUPERSEDED BY: …`). That is the recommended way to
-  change a decision: write the new note with `supersedes` instead of deleting
-  history.
-- `memoria doctor` reports dangling links and fact pairs that look contradictory
-  (same wording, opposite polarity).
-
-### Note format
-
-Notes are markdown with optional YAML frontmatter. Frontmatter is written
-automatically on the first `memoria_write`; hand-written notes without it are
-still indexed (the title comes from the first `#` heading, the category from the
-folder).
-
-```markdown
----
-id: mem_1758712445123_a1b2c3
-title: Dietary preferences          # broad topic = note title
-topic: Dietary preferences           # drives the file name: dietary-preferences.md
-category: preferences
-tags: [alice, dietary, food]
-aliases: ["Dairy", "Food preferences"]
-related: []
-supersedes: []
-created: 2025-09-24T09:14:05.123Z
-updated: 2025-09-24T09:14:05.123Z
-last_used: 1758712445123            # refreshed lazily on recall
-source: agent
-confidence: high
-priority: normal
-summary: Oat milk in coffee; lactose intolerant.
----
-
-# Dietary preferences
-
-## Facts
-
-- **Drinks** — Drinks oat milk in flat whites; avoids dairy.
-- **Fruit** — Likes apples and pears; dislikes durian.
+```text
+~/.pi/agent/memoria/
+├── MEMORY.md
+├── config.json           # optional settings
+├── library/
+│   ├── people/
+│   ├── projects/
+│   └── preferences/
+├── .index/               # rebuildable search data
+└── .trash/               # recoverable deleted notes
 ```
 
-Fields: `topic` (broad grouping, drives the file name), `priority`
-(`low|normal|high|critical`, boosts ranking), `confidence`, `tags`, `aliases`
-(all indexed), `related`, `supersedes`, `summary` (used in listings and recall),
-`last_used` (maintained by the store), and `category` (kept in sync with the
-folder). Unknown keys are preserved verbatim through updates.
-
-## Tools
-
-| Tool | Purpose |
-|---|---|
-| `memoria_recall` | Search long-term memory. Filters by category, tags, priority, recency, scope; options for `include_body`, `min_score`, `explain`, `rerank`, `drop_superseded`, prefix/fuzzy control. |
-| `memoria_write` | Add a fact to a broad **topic note** (`topic`, `content`, optional `label`, category, tags, aliases, related, supersedes, summary, priority). Creates the note on first use and appends afterwards. |
-| `memoria_read` | Read a full note by id, path or alias, with its aliases, related notes and superseding notes. |
-| `memoria_move` | Re-file a note under a better broad topic (`from`, `topic`, optional `category`, `merge`, `keep_alias`). Renames when the target is free; set `merge: true` to combine with an occupied target. |
-| `memoria_sessions` | Search the transcripts of earlier conversations (`action: "search"`, plus `since_days`, `project`, `include_tools`, `user_only`) and read the surrounding dialogue (`action: "read"`, `path`, `line`, `window`) before quoting it. |
-| `memoria_hot` | Read/add/remove/replace/compact `MEMORY.md`, the always-in-context briefing. |
-| `memoria_list` | Browse categories, titles, ids, tags, aliases and summaries. |
-| `memoria_forget` | Move a note to `.trash/` (recoverable). |
-| `memoria_export` | Dump the store to JSONL, inline or to a file. |
-| `memoria_import` | Restore from JSONL (`mode: merge|replace|skip`, `dry_run`). |
-
-The agent's system prompt teaches it when to use them, so you normally do not
-have to ask.
-
-## Commands
-
-```
-/memoria                     Store status, index stats, MEMORY.md budget
-/memoria search <query>      Ranked results with snippets (--primary/--project/--all)
-/memoria store <text>        Quick capture into library/inbox
-/memoria read <id|path>      Print a full note
-/memoria move <ref> <topic> [--merge]  Re-file a note; opt into merging an occupied target
-/memoria hot                 Show MEMORY.md
-/memoria topics              Review notes: facts, size, usage, merge candidates
-/memoria diff [days]         Memories created or updated recently (default 7 days)
-/memoria sessions <query>    Search earlier conversations (--days=N --project=X --tools --user)
-/memoria sessions --read <path> <line> [--window=N]   Show the surrounding dialogue
-/memoria doctor              Consistency problems and housekeeping hints
-/memoria export [file]       Dump the store to JSONL (default ./memoria-export-<date>.jsonl)
-/memoria export --hot [file] Write MEMORY.md alone as an "about me" document
-/memoria import <file>       Restore from JSONL (--merge|--replace|--skip, --dry-run)
-/memoria learn               Extract durable memories from the current session
-/memoria reindex             Rebuild the search index from disk
-/memoria index               Regenerate library/INDEX.md files
-/memoria paths               Print store paths
-/memoria forget <id>         Move a note to .trash
-```
+If you set `PI_CODING_AGENT_DIR`, the store follows that directory. You can read
+and edit notes with a text editor; the index picks up changes automatically.
 
 ## Configuration
 
-Create `config.json` in the store root (`~/.pi/agent/memoria/config.json`) to
-override any default. Everything is optional; unknown or malformed values fall
-back to the default rather than failing.
+Create `~/.pi/agent/memoria/config.json` to override defaults. For example, to
+add a project store and teach search an abbreviation:
 
 ```json
 {
-  "autoRecall": true,
-  "autoRecallLimit": 6,
-  "topicMaxWords": 6,
-  "exclude": ["library/scratch"],
   "projectRoot": ".pi/memoria-project",
-  "autoLearn": "on-settle",
   "synonyms": { "k8s": ["kubernetes"] }
 }
 ```
 
+The primary store is user-wide. `projectRoot` adds an optional writable project
+store; `extraRoots` adds read-only stores. Reranking is off by default because
+it makes an additional model call per search.
+
+<details>
+<summary>All configuration options</summary>
+
 | Key | Default | Meaning |
 |---|---:|---|
 | `rootDir` | `"$AGENT_DIR/memoria"` | Primary store. Supports `$AGENT_DIR`, `~/`, absolute and cwd-relative paths. |
@@ -370,9 +118,10 @@ back to the default rather than failing.
 | `hotLimit` | `5000` | Hard cap for `MEMORY.md`, in characters. |
 | `snippetChars` | `280` | Body excerpt length per hit. |
 | `autoRecall` | `true` | Search the library on every user prompt. |
-| `autoRecallLimit` | `6` | Maximum notes injected per prompt. |
+| `autoRecallLimit` | `3` | Maximum notes injected per prompt. |
+| `autoRecallMinRatio` | `0.3` | Automatic hits must score at least this fraction of the strongest eligible hit; set to `0` to disable the relative cutoff. |
 | `autoRecallMinScore` | `1.4` | Score floor for auto-recall. |
-| `autoRecallMaxChars` | `2400` | Character budget for the injected recall block. |
+| `autoRecallMaxChars` | `2400` | Strict total character budget, including wrappers and transcript fallback. |
 | `autoRecallLastTurns` | `1` | Previous turns folded into the recall query. |
 | `autoRecallPriorWeight` | `0.4` | Weight of those previous turns versus the current prompt. |
 | `bodyCacheBytes` | `8388608` | In-memory body cache budget. |
@@ -397,11 +146,6 @@ back to the default rather than failing.
 | `rerankModel` | `""` | Model id (`provider/model`); empty uses the session model. |
 | `rerankTopK` | `12` | Candidates shown to the reranker. |
 | `rerankTimeoutMs` | `2500` | Reranker budget before falling back to lexical order. |
-| `autoLearn` | `"off"` | `off`, `on-settle` (after the agent goes idle) or `on-shutdown`. |
-| `autoLearnMinTurns` | `8` | Minimum user turns before automatic extraction. |
-| `autoLearnMinChars` | `2000` | Minimum transcript size before automatic extraction. |
-| `autoLearnCooldownMs` | `21600000` | Minimum gap between automatic extractions. |
-| `learnChunkChars` | `12000` | Characters per extraction chunk (long sessions are chunked). |
 | `indexFormat` | `"auto"` | `auto` (binary above 20k notes), `json` or `binary`. |
 | `sessionSearch` | `true` | Search saved session transcripts at all. |
 | `sessionRoots` | `[]` | Extra transcript roots (searched before `<agent dir>/sessions`). |
@@ -412,282 +156,69 @@ back to the default rather than failing.
 | `sessionIncludeTools` | `false` | Include tool calls/results and compaction summaries by default. |
 | `sessionRipgrep` | `true` | Use a ripgrep prefilter to skip match-free transcripts when `rg` is available; without it the slower built-in scanner runs. |
 
-## Scopes: personal, project, read-only
-
-- **`primary`** (default) — the user-level store at `<agent dir>/memoria`.
-  Memories follow you across projects.
-- **`project`** — set `projectRoot` to keep project-specific memories in the
-  repository (`"projectRoot": ".pi/memoria-project"`). It is writable: pass
-  `scope: "project"` to write there, while reads default to `all`.
-- **`all`** — primary + project + extra roots, read paths merged.
-- **`extraRoots`** — additional stores that are always **read-only**, for a
-  shared team library or an imported archive.
-- **`global`** — legacy alias for `primary`.
-
-Cross-store results are rank-normalized: a small store's best hit is lifted to
-the global best (up to 4×) instead of being drowned by a large one, and a note
-that exists in two stores is returned once.
-
-## Synonyms
-
-Domain shorthand rarely appears in the notes you wrote earlier. Drop a
-`synonyms.json` in the store root (or inline the table in `config.json`) and
-expansion happens at query time, both directions, with no re-indexing:
-
-```json
-{
-  "k8s": ["kubernetes"],
-  "postgres": ["postgresql", "pg"],
-  "auth": ["authentication", "login"],
-  "oncall": ["on-call", "pager"]
-}
-```
+</details>
 
-## Model reranking
+## Privacy and limits
 
-BM25 is exact but literal: it does not know which of five plausible notes you
-mean. With `"rerank": true`, the top candidates (`rerankTopK`) are shown to the
-session model, which returns them in relevance order, within
-`rerankTimeoutMs`. Reranking is strictly best-effort: on timeout, error, missing
-auth or an unparsable reply, lexical order is used, so it can never make recall
-fail. It is off by default because it costs a model call per search.
+**Local storage does not mean model-private memory.** The briefing, recalled
+notes and returned transcript excerpts become part of the configured model's
+context. With a hosted model, that content is sent to its provider. Reranking
+also sends content to the configured model when enabled.
 
-## Automatic session learning
+- Notes are not encrypted, and memoria does not detect or redact credentials.
+  Do not store secrets.
+- Search is lexical (BM25 with aliases, synonyms, prefix and fuzzy matching),
+  not embedding-based. It can miss a paraphrase with no matching terms.
+- Recall is bounded. Relevant notes can be omitted by score or context limits;
+  transcript searches report `partial` when they run out of scan budget.
+- Reranking can reorder retrieved notes, not find notes that search missed.
+- Deletes move notes to `.trash/`. This is recovery, not secure erasure.
+- Writes use atomic file replacement, but separate pi processes are not
+  coordinated as concurrent writers. Keep backups.
 
-`/memoria learn` extracts durable facts from the current session. Long
-conversations are chunked (`learnChunkChars`, at most 4 calls) and progress is
-shown in the status line. Set `autoLearn` to `"on-settle"` (after the agent
-finishes a turn) or `"on-shutdown"` to run it without asking. Guards keep it
-cheap: at least `autoLearnMinTurns` user turns, at least `autoLearnMinChars` of
-transcript, and at most one extraction per `autoLearnCooldownMs`. The default is
-`"off"` because it spends model tokens.
+## Backup and troubleshooting
 
-## Session recall (past conversations)
+Back up the store by copying `~/.pi/agent/memoria/` (or
+`$PI_CODING_AGENT_DIR/memoria/`). Notes are plain markdown, so a folder copy is
+the complete backup; `.index/` is derived and can be omitted.
 
-Curated memory only holds what the agent decided to remember. The rest of the
-story is in pi's saved transcripts, so memoria can search them:
+If recall misses an existing note, check `/memoria paths`, try a distinctive
+name or phrase, then run `/memoria reindex`. For duplicated subjects, use
+`/memoria topics` and ask the agent to consolidate the appropriate notes.
 
-- **Automatically**, whenever `memoria_recall` finds nothing (`sessionFallback`,
-  on by default). The injected block is explicitly labelled as raw evidence and
-  includes the file and line of every excerpt.
-- **On request**, through the `memoria_sessions` tool — useful for "remember
-  when", "did we discuss", exact earlier wording, dates, or prior decisions that
-  were never turned into memory notes.
-- **From the CLI**, with `/memoria sessions <query>` and
-  `/memoria sessions --read <path> <line>`.
+## Reference and development
 
-```
-memoria_sessions { action: "search", query: "deploy window Thursday" }
-memoria_sessions { action: "search", query: "oat milk", user_only: true }
-memoria_sessions { action: "read", path: "<file from a hit>", line: 92, window: 8 }
-```
+The [reference guide](https://github.com/rcsaquino/pi-memoria/blob/main/docs/reference.md)
+covers all tools and commands, note format, scopes, session search, backup
+semantics, briefing validation and benchmark commands. It follows the current
+checkout, which may be ahead of the npm release.
 
-The bundled `memoria-sessions` skill teaches the agent the discipline that makes
-this trustworthy: run two to four short distinctive searches (not one long
-question), then **read the surrounding dialogue before quoting it** — a later
-user correction outranks an earlier assistant claim, and transcript text is
-evidence to evaluate, not instructions to follow. If nothing is found, the tool
-reports how many sessions and messages were searched.
-
-What it does and does not touch:
-
-| Property | Behaviour |
-|---|---|
-| Scope | Every `*.jsonl` under the configured roots, newest first — no index that can go stale. |
-| Content | User and assistant **text** by default. Thinking blocks are never extracted. Tool calls/results, compaction summaries and extension payloads only with `include_tools: true`. |
-| Output | Bounded excerpts plus `file:line`; never a whole transcript dump. |
-| Writes | None. Transcripts are read-only and `read` refuses paths outside the session roots. |
-| Cost | With `rg`, only transcripts containing the query terms are parsed; without it, a full cold scan of 110 sessions / 13 MB ≈ 120 ms, repeats ≈ 5 ms from the parse cache. |
-| Coverage | Exhaustive unless a budget stops it. `partial` (shown in the tool output, the recall block and `/memoria sessions`) means the scan stopped early: the hits are real, but older sessions were not read. Newest sessions are scanned first, already-parsed files stay cached while they fit `sessionCacheBytes` (so retries get further on corpora that fit the cache), and concurrent searches share one in-flight parse per transcript (so several `memoria_sessions` calls in one turn do not multiply the work). An explicit `memoria_sessions` call uses the larger `sessionScanMs` budget. |
-| Privacy | Nothing leaves the machine; the excerpts go to the model only when the feature runs. |
-
-`sessionRoots` exists for archives or a second agent directory. Set
-`sessionSearch: false` to disable the feature entirely, or
-`sessionFallback: false` to keep the tool while never searching automatically.
-
-When `rg` is available (pi ships it and puts it on `PATH`), a selective search
-asks ripgrep which transcripts contain the query terms and parses only those, so
-even a gigabyte-scale history is answered within the normal budget. If `rg` is
-missing or fails, memoria falls back to reading every transcript itself and says
-so: the result carries a `ripgrep is not installed` note, and interactive mode
-shows it once per session. Large histories may then be only partially covered.
-
-Without `rg` (or for a deliberately disabled accelerator), the default
-`sessionScanMs` budget and `sessionCacheBytes` cache cover only part of a large
-corpus: searches report `partial`, and repeats are cold scans because the cache
-cannot retain the parsed files. Raise `sessionScanMs` so an explicit
-`memoria_sessions` call can cover the whole corpus in one pass, and
-`sessionCacheBytes` only if you have the RAM for the parsed messages (at this
-scale that means gigabytes). The automatic fallback remains capped at 400 ms,
-so on such a corpus it is always a partial scan.
-
-## Backup and migration
-
-`memoria_export` writes JSONL — one record per line, notes plus `MEMORY.md` — to
-a file or returns a bounded preview. `memoria_import` restores it:
+To work on the extension from a clone:
 
-```
-memoria_export { path: "memoria-backup.jsonl" }
-memoria_import { path: "memoria-backup.jsonl", dry_run: true }
-memoria_import { path: "memoria-backup.jsonl", mode: "merge" }
+```sh
+npm install
+npm run typecheck
+npm test
+npm run eval
+npm run bench
+pi -e ./index.ts
 ```
 
-- `merge` (default) adds facts that are missing, never duplicating an id.
-- `replace` overwrites notes with the same id.
-- `skip` only imports notes that do not exist yet.
-- Notes keep their ids, so ids in an old transcript still resolve.
-- Paths are validated: an import cannot write outside `library/`, and a path
-  already taken by a different note gets a numbered sibling instead of an
-  overwrite.
-
-The same files remain readable as plain markdown if you stop using memoria, and
-the whole store is safe to commit to a private repository (`.index/` is derived
-and can be deleted).
-
-## Performance
-
-`node tests/bench.ts 1000 5000` measures a worst-case corpus (50-word
-vocabulary, 60-word documents, so every posting list is long);
-`node tests/bench.ts 1000 5000 --real` uses a realistic high-vocabulary corpus
-(~44k distinct terms at 5k notes).
-
-| Corpus | Notes | Index size | Cold load | Reload | Search | Prefix | Fuzzy |
-|---|---:|---:|---:|---:|---:|---:|---:|
-| worst case | 1,000 | 1.3 MB | 219 ms | 23 ms | 0.35 ms | 0.22 ms | 0.32 ms |
-| worst case | 5,000 | 6.8 MB | 1.10 s | 109 ms | 0.89 ms | 0.66 ms | 0.94 ms |
-| realistic | 5,000 | 8.5 MB | 1.34 s | 134 ms | 1.20 ms | 0.64 ms | 1.02 ms |
-| realistic | 20,000 | 34.5 MB | 5.4 s | 543 ms | 5.88 ms | 2.63 ms | 4.30 ms |
-
-Auto-recall runs on every prompt, which is why the search path is
-allocation-light: a dense scratch-buffer BM25 loop, posting lists in memory, and
-snippets read only for the final hits. Recency scans are throttled
-(`scanIntervalMs`) and coalesced from filesystem events (`watcherSettleMs`), so
-a burst of edits costs one refresh.
-
-## Privacy and durability
-
-- **Local only.** Nothing is sent anywhere except by the optional reranker and
-  session learning, which use the model you already configured and only when
-  enabled.
-- **Files, not a database.** Memoria never owns your data: notes are markdown
-  with frontmatter, deletes are soft (moved to `.trash/`), and the index is
-  derived and can be rebuilt with `/memoria reindex`.
-- **Crash-safe moves.** Category moves, renames and merges are journaled. On
-  restart, a merge only removes its source after the target has all its facts
-  and the source's former id.
-- **Atomic writes.** Every write goes through a temp file and rename; there is no
-  window where a note is half-written.
-- **Scoped reads.** `memoria_read` only follows paths inside the memory library;
-  transcript window reads refuse paths or symlinks outside configured roots.
-- **Secrets:** memoria does not scan for credentials, and the learn prompt tells
-  the model not to store them. If you keep secrets in the store anyway, remember
-  that recall may surface them in model context — treat the store like your shell
-  history.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Notes exist but recall finds nothing | `/memoria reindex`; check `/memoria paths` for the store location; remember scopes (`--all` searches every root). |
-| A note is filed under `people.md` instead of the person's name | The topic was rejected as fact-shaped or relational. Write with the person's name as `topic` and put the relationship in the content. |
-| The same subject ended up in two notes | `/memoria topics` lists merge candidates with the exact `memoria_move` command; `memoria doctor` reports them too. |
-| `MEMORY.md` is over budget | `memoria_hot { action: "compact" }` drops the least important trailing paragraphs and returns them so you can file them into notes. |
-| A decision changed | Write the new note with `supersedes: ["<old id, path or title>"]`; the old note stays searchable but is demoted and flagged. |
-| Search misses domain shorthand | Add `synonyms.json` (see [Synonyms](#synonyms)). |
-| Model reranking is slow | Lower `rerankTopK`, or leave `rerank` off — lexical search is already sub-millisecond. |
-| Want to see what changed lately | `/memoria diff 3` for the last three days, `/memoria topics` for usage, and a session-start notification summarises changes since your previous session. |
-| An agent edited files and the index is stale | Filesystem events and a throttled scan pick changes up automatically; `/memoria doctor` shows the state. |
-| The user references something from before | The agent should search transcripts (`memoria_sessions`, or `/memoria sessions <query>`) rather than claim it does not remember; `/memoria paths` lists the session roots. |
-| Session search finds nothing | Try different wording, a name or a date, or `include_tools: true`; check `sessionRoots` covers the transcript location, and note that a budget-limited scan reports `partial`. |
-
-## Development
-
-```bash
-npm install            # dev-only: pi host packages + typescript
-npm test               # node:test, no build step
-npm run typecheck      # tsc --noEmit
-npm run eval           # recall@1/@5/MRR over the fixture corpus
-npm run bench          # latency at 1k and 5k notes
-npm run bench:real     # realistic high-vocabulary corpus
-pi -e ./index.ts       # run the extension from the checkout
-```
+No build step is needed. See
+[AGENTS.md](https://github.com/rcsaquino/pi-memoria/blob/main/AGENTS.md)
+for architecture, invariants and contribution checks.
 
-The extension runs on Node's native type-stripping (`node >= 22.19`), which
-means no build step but also no `enum`, `namespace`, constructor parameter
-properties or `import x = require()` in the sources. Type-only imports must use
-`import type`, and relative imports include the `.ts` extension.
+Report bugs through [GitHub Issues](https://github.com/rcsaquino/pi-memoria/issues).
+Include your pi and Node versions, steps to reproduce, and relevant errors.
+Remove personal memory content and credentials before sharing logs.
 
-Architecture, invariants and the release checklist live in
-[`AGENTS.md`](AGENTS.md). The short version:
+## Support My Work
 
-```
-index.ts            lifecycle hooks, system-prompt section, auto-recall, auto-learn
-src/types.ts        shared types (no runtime imports)
-src/util.ts         atomic writes, mutex, debounce, ids, paths
-src/frontmatter.ts  dependency-free YAML-subset parser/serializer
-src/tokenize.ts     identifiers, camel/snake/kebab, CJK, stemmer, trigrams
-src/config.ts       defaults, coercion, path resolution
-src/store.ts        filesystem: parse, write, merge, move, MEMORY.md, indexes
-src/index-engine.ts inverted index, persistence (JSON/binary), link resolution
-src/search.ts       BM25, boosts, snippets, explain, related/superseded handling
-src/similarity.ts   duplicate-topic and contradiction detection
-src/usage.ts        hits/writes/last-used tracking
-src/timeexpr.ts     "last week" → recency windows
-src/synonyms.ts     query-side synonym tables
-src/transfer.ts     JSONL export/import
-src/learn.ts        session extraction (chunked)
-src/recall.ts       prompt/message rendering
-src/rerank.ts       optional model reranking
-src/runtime.ts      roots, locks, caching, health, export/import, scopes
-src/tools.ts        tool definitions and renderers
-src/commands.ts     /memoria subcommands
-```
+If pi-memoria is useful to you, please consider supporting my work by
+[buying me a coffee](https://ko-fi.com/rcsaquino). 😊
 
-### Publishing your own copy
-
-1. Push the repository to GitHub (public or private).
-2. Keep `index.ts` at the package root and the `pi` manifest in `package.json`.
-3. Leave the host modules as `peerDependencies` **and** mark them
-   `"optional": true` in `peerDependenciesMeta`, keeping them in
-   `devDependencies` for local tests only. Without that, npm installs a ~450 MB
-   duplicate of pi into the package.
-4. Tag releases (`git tag v<version> && git push --tags`) and install by tag:
-   `pi install git:github.com/<you>/pi-memoria@v<version>`.
-5. `npm pack --dry-run` should list only `index.ts`, `src/**`, `skills/**`,
-   `README.md`, `LICENSE` and `package.json`.
-
-## Design notes and limits
-
-- **Topic notes are the unit of storage.** This is deliberately opinionated: a
-  file per fact fragments knowledge and makes retrieval worse. The cost is that
-  the agent must pick a broad topic; when it picks badly, the store falls back to
-  the category rather than creating a bad file name, and `memoria_move` fixes it
-  later.
-- **Lexical, not semantic.** BM25 with a conservative stemmer, prefix and fuzzy
-  matching is fast, deterministic and dependency-free, but it will not connect
-  "my manager" to "Alice" without an alias or a synonym table. Embeddings would
-  improve that; they are not worth the dependency for a store this fast.
-- **Cross-topic duplication is reported, not merged automatically.** The store
-  flags two notes as duplicates only when their *names* also point at the same
-  subject (equal slugs, or one name being a prefix/suffix of the other — e.g.
-  `Alice` and `Alice Smith`, or a legacy `Johns father` note whose name appears
-  as an alias). Content overlap alone is not enough: one person's note naturally
-  describes the people around them, and merging John Doe with his father would be
-  worse than missing a duplicate. Folding notes stays an explicit
-  `memoria_move`, suggested on write and listed by `/memoria topics`.
-- **Usage is derived data.** `.index/usage.json` drives staleness and promotion
-  hints; deleting `.index/` only loses those hints.
-- **Journal recovery covers moves, not arbitrary edits.** A crash between an
-  atomic write and a trash move is repaired; a crash mid-edit of a single file
-  leaves the previous content intact (writes are atomic).
-- **Model reranking instead of embeddings.** An embedding index would improve
-  semantic matching, but pi exposes chat completions rather than an embedding
-  API, and a vector store is a dependency this project does not want. The
-  optional reranker gets the same effect (an LLM judging the top candidates) and
-  degrades to lexical order on any failure. Time-scoped questions are handled by
-  parsing the window out of the query rather than by time-decayed IDF: the note's
-  own timestamp is the signal that matters.
+<a href="https://ko-fi.com/rcsaquino" target="_blank" rel="noopener noreferrer"><img height="72" src="https://storage.ko-fi.com/cdn/kofi2.png?v=3" alt="Buy Me a Coffee at ko-fi.com" /></a>
 
 ## License
 
-MIT © 2026 rcsaquino. See [LICENSE](LICENSE).
+[MIT](https://github.com/rcsaquino/pi-memoria/blob/main/LICENSE) © 2026 rcsaquino.