minnimemory 1.3.7 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +45 -0
- package/README.md +51 -5
- package/package.json +2 -2
- package/pkg/chunks/chunk-K7XLQMXJ.js +166 -0
- package/pkg/chunks/chunk-SELGA237.js +54 -0
- package/pkg/chunks/{mcpServer-2FYD5LS3.js → mcpServer-6J4GLXHP.js} +1 -1
- package/pkg/cli.js +132 -94
- package/pkg/index.js +1 -1
- package/pkg/chunks/chunk-B5ETYKWT.js +0 -54
- package/pkg/chunks/chunk-CR5T6SUD.js +0 -162
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,51 @@
|
|
|
3
3
|
All notable changes to the `minnimemory` package. Dates are publish dates; an entry that has not
|
|
4
4
|
been published yet says `unreleased` and gets its date on the day it goes out.
|
|
5
5
|
|
|
6
|
+
## 1.4.0 - 2026-10-27
|
|
7
|
+
|
|
8
|
+
- Changed: a first sort of a memory folder that grows what is loaded every turn (the index gets
|
|
9
|
+
longer, nothing is saved) is now verdict `leave`: `apply` refuses it without `--force`
|
|
10
|
+
(`force: true` over MCP) and says how many tokens it would add. A re-apply still sorts.
|
|
11
|
+
- Changed: `apply` on a memory folder cuts an index hook over the 120 character cap (MM006) to
|
|
12
|
+
fit, but only when every word of it is in the linked file's frontmatter `description:`;
|
|
13
|
+
otherwise the line is kept whole. Undo restores the index byte for byte.
|
|
14
|
+
- Changed: `apply` on a memory folder swaps the link targets of two index lines that each
|
|
15
|
+
describe the other's file (MM019); any other MM019 line is still a flag only. MM019 no longer
|
|
16
|
+
flags a line whose own file holds half its words when the better match has its own line.
|
|
17
|
+
- Added: verdict `fix`. When a first sort of a memory folder with no imported file is refused
|
|
18
|
+
because it grows the prefix, `apply` still fixes the index's own lines (the MM006 cuts and
|
|
19
|
+
MM019 swaps above) and moves no file, as long as that shrinks the prefix. `--force`
|
|
20
|
+
(`force: true` over MCP) sorts anyway; a folder applied fix-only stays that way on a re-apply,
|
|
21
|
+
and `undo` restores the index byte for byte.
|
|
22
|
+
- Fixed (live Codex check, T7): `install --host codex` passes a `CODEX_HOME` you set on to the
|
|
23
|
+
server (`codex mcp add --env`, or an `env` line in the printed TOML block). Codex starts an
|
|
24
|
+
MCP server without it, so the server read and wrote `~/.codex` instead.
|
|
25
|
+
- Fixed (T7): the Codex map, MM022 and the apply cap check follow what Codex really does: the
|
|
26
|
+
user `AGENTS.md` does not count toward `project_doc_max_bytes`, and the project file that
|
|
27
|
+
crosses the cap is cut there (the map says `PART: first N bytes`), not dropped whole.
|
|
28
|
+
- Added: Codex as a second host (DESIGN.md 7.2). `install --host codex` registers the server
|
|
29
|
+
with `codex mcp add` (the served command carries `--host codex`), writes the two
|
|
30
|
+
`UserPromptSubmit` hooks to `~/.codex/hooks.json` or `<repo>/.codex/hooks.json`, prints the
|
|
31
|
+
TOML block when `codex` is not on PATH, and `uninstall --host codex` removes exactly that.
|
|
32
|
+
- Added: the Codex load model. `init` maps the `AGENTS.md` chain (user file, root to working
|
|
33
|
+
directory, `AGENTS.override.md` first, `project_doc_fallback_filenames`) with each file's
|
|
34
|
+
bytes and whether it reaches the model under `project_doc_max_bytes`, read from
|
|
35
|
+
`~/.codex/config.toml` and `<repo>/.codex/config.toml`. No report is needed on Codex.
|
|
36
|
+
- Added: MM022 (a file on the chain past Codex's cap never reaches the model; high) and MM023
|
|
37
|
+
(`AGENTS.override.md` shadows `AGENTS.md`; low). Both run only for a Codex host.
|
|
38
|
+
- Changed: a project whose compile target is `AGENTS.md` (or `AGENTS.override.md`) and that has
|
|
39
|
+
no `.claude/` folder now routes to `OnDemandMemory/` beside the file, so one folder serves
|
|
40
|
+
Codex, Cursor and Claude Code. A root compiled before keeps the folder its manifest names.
|
|
41
|
+
- Changed: `apply` on Codex refuses a plan whose compiled host would still be over the cap and
|
|
42
|
+
says what to cut; the printed apply command carries `--host codex`.
|
|
43
|
+
- Changed: `init`, `doctor`, `apply`, `undo`, `hook`, `drift` and `mcp` take `--host claude|codex`;
|
|
44
|
+
the discovery record and the hook's session stamps live under the host's config dir
|
|
45
|
+
(`CLAUDE_CONFIG_DIR`/`~/.claude`, `CODEX_HOME`/`~/.codex`). A Codex user's `AGENTS.md` has no
|
|
46
|
+
`@` imports: lines that look like one are text there and are not followed.
|
|
47
|
+
- Not changed: the MCP tool schemas (the host comes from the server's `--host`, not a per-call
|
|
48
|
+
argument; measured 2026-10-26: one optional enum on four schemas cost 185 tokens every session).
|
|
49
|
+
The frozen interface text is untouched.
|
|
50
|
+
|
|
6
51
|
## 1.3.7 - 2026-10-22
|
|
7
52
|
|
|
8
53
|
- Fix (#23): the prompt hook printed nothing when the best memory section was over its 400-token
|
package/README.md
CHANGED
|
@@ -148,8 +148,52 @@ the package on every prompt and measured 1.3 to 1.7 s. `--no-hook` skips it at i
|
|
|
148
148
|
`install --remove` takes out both the MCP registration and the hook entry it added, leaving
|
|
149
149
|
every other key and every other hook in your Claude Code settings untouched.
|
|
150
150
|
|
|
151
|
-
|
|
152
|
-
|
|
151
|
+
## Install for Codex
|
|
152
|
+
|
|
153
|
+
Codex loads one chain of `AGENTS.md` files every turn: `$CODEX_HOME/AGENTS.md`, then one file
|
|
154
|
+
per folder from the repo root down to your working directory. The project files share
|
|
155
|
+
`project_doc_max_bytes` (32 KiB by default): the file that crosses it is cut there and nothing
|
|
156
|
+
after it is added. Nothing loads on demand, so a long `AGENTS.md` is paid in full on every turn
|
|
157
|
+
and whatever sits past the cap never reaches the model. The same four verbs trim it the same way.
|
|
158
|
+
|
|
159
|
+
```
|
|
160
|
+
npx -y minnimemory install --host codex
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
This runs `codex mcp add minnimemory -- npx -y minnimemory mcp --host codex` (printed, and
|
|
164
|
+
idempotent) and adds the two `UserPromptSubmit` hooks to `~/.codex/hooks.json` (`--scope
|
|
165
|
+
project` writes `<repo>/.codex/hooks.json`; Codex has no local scope). Without the `codex`
|
|
166
|
+
binary it prints the `[mcp_servers.minnimemory]` block to paste into `~/.codex/config.toml`
|
|
167
|
+
and exits 2. Then open Codex, run `/hooks` once to trust the two minnimemory hooks (Codex skips
|
|
168
|
+
an untrusted hook), and ask it to run `init`. In a terminal: `npx -y minnimemory init . --host
|
|
169
|
+
codex`. Codex's load set is fully determined by the files and `config.toml`, so `--from-log` and
|
|
170
|
+
`--loaded` are not needed; the host is detected when `CODEX_HOME` is set or your Codex config
|
|
171
|
+
registers minnimemory, and `--host codex` pins it. If you set `CODEX_HOME`, install passes it
|
|
172
|
+
on to the server (`--env CODEX_HOME=...`), because Codex starts MCP servers without it.
|
|
173
|
+
|
|
174
|
+
In `codex exec` (no one to approve a tool call), Codex refuses MCP calls that need approval.
|
|
175
|
+
The four verbs only read, so you can let them run without asking:
|
|
176
|
+
|
|
177
|
+
```toml
|
|
178
|
+
[mcp_servers.minnimemory]
|
|
179
|
+
default_tools_approval_mode = "approve"
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
Codex does not show MCP prompts, so the `/mcp__minnimemory__<verb>` slash commands are Claude
|
|
183
|
+
Code only; in Codex, ask for the verb by name.
|
|
184
|
+
|
|
185
|
+
What is different on Codex: the map shows the chain (layer, file, bytes, loaded) and the cap in
|
|
186
|
+
force (a file cut by the cap shows `PART: first N bytes`); `doctor` adds MM022 (a file past the cap) and MM023 (`AGENTS.override.md` shadowing an
|
|
187
|
+
`AGENTS.md`); `apply` compiles the `AGENTS.md` Codex reads (the override file when present),
|
|
188
|
+
puts routed pieces in `OnDemandMemory/` beside it when the repo has no `.claude/` folder, and
|
|
189
|
+
refuses a plan whose compiled file would still be over the cap. The discovery record lives
|
|
190
|
+
under `$CODEX_HOME/minnimemory/`. Nested `AGENTS.md` files below the root are listed with their
|
|
191
|
+
size and not compiled. Codex's own `memories` feature is Codex-managed and never touched.
|
|
192
|
+
Measured on Claude Code; Codex measurement in progress (section 8 of the design).
|
|
193
|
+
|
|
194
|
+
**Other MCP hosts** (Cursor, Windsurf, Claude Desktop, SDK clients): `install --host cursor`
|
|
195
|
+
and `--host windsurf` print the `mcpServers` entry to paste, but the hook and the load model are
|
|
196
|
+
not built for them, and nothing there is exercised end to end.
|
|
153
197
|
|
|
154
198
|
## Use it
|
|
155
199
|
|
|
@@ -471,7 +515,7 @@ add` line above, turns on the memory hook and the drift notice hook, and prints
|
|
|
471
515
|
| `--force` | remove an existing registration first, then re-add |
|
|
472
516
|
| `--no-hook` | skip the three hooks (memory, drift notice, load log; on by default) |
|
|
473
517
|
| `--remove` | remove the MCP registration and the hooks `install` added; the same as `minnimemory uninstall` |
|
|
474
|
-
| `--host <name>` | `cursor`, `windsurf` or `json`: print the `mcpServers` snippet to paste (and the config file for Cursor and Windsurf) instead of registering with Claude Code; no hook |
|
|
518
|
+
| `--host <name>` | `codex`: register with Codex (`codex mcp add`) and write the two hooks to `~/.codex/hooks.json` or `<repo>/.codex/hooks.json`, see Install for Codex. `cursor`, `windsurf` or `json`: print the `mcpServers` snippet to paste (and the config file for Cursor and Windsurf) instead of registering with Claude Code; no hook |
|
|
475
519
|
|
|
476
520
|
Idempotent: an existing registration is reported, with the command to change it, not duplicated.
|
|
477
521
|
Without the `claude` CLI on `PATH` it prints the manual line and a JSON snippet instead, exit 2;
|
|
@@ -610,8 +654,10 @@ The opposite. Splitting volatile content out of the always-loaded prefix is prec
|
|
|
610
654
|
the cache valid across sessions.
|
|
611
655
|
|
|
612
656
|
**Does it work with Cursor or Codex?**
|
|
613
|
-
|
|
614
|
-
|
|
657
|
+
Codex: yes, since 1.4.0 (see Install for Codex): the same four verbs on the `AGENTS.md` chain
|
|
658
|
+
Codex loads, with its byte cap as a second ceiling. Cursor: the MCP server runs there
|
|
659
|
+
(`install --host cursor` prints the entry) but the hook and the load model are not built, and
|
|
660
|
+
nothing there is exercised end to end.
|
|
615
661
|
|
|
616
662
|
## License
|
|
617
663
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "minnimemory",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.4.0",
|
|
4
4
|
"description": "MinniMemoryMCP: an MCP server that gives an AI coding agent curated memory. Tools audit the agent's memory file, compile it into a small AlwaysOnMemory body plus OnDemandMemory files, serve it back on demand and keep it maintained. Deterministic, lossless, offline. Built by MinniAI.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"mcpName": "io.github.MinniAI-com/minnimemory",
|
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
"homepage": "https://minniai.com",
|
|
10
10
|
"repository": {
|
|
11
11
|
"type": "git",
|
|
12
|
-
"url": "https://github.com/MinniAI-com/minnimemory-plugin.git"
|
|
12
|
+
"url": "git+https://github.com/MinniAI-com/minnimemory-plugin.git"
|
|
13
13
|
},
|
|
14
14
|
"bugs": "https://github.com/MinniAI-com/minnimemory-plugin/issues",
|
|
15
15
|
"publishConfig": {
|