memgineering 0.18.1 → 0.18.2

package/CHANGELOG.md

@@ -11,6 +11,23 @@ language the reader wants. The bilingual rule the monorepo applies to
 
 ## [Unreleased]
 
+## [0.18.2] — 2026-08-31
+
+### Fixed
+
+- **Setup no longer contradicts itself about Codex hooks.** Codex installs the
+  two hooks and runs neither until you answer a review panel; setup said so and
+  then announced two lines later that the hooks all worked. On a Codex install
+  it now says recall and remember work and the hooks start after that review.
+- **The Codex hook notice names the key.** Press `t` to trust them. It also says
+  that the trust is recorded per hook content, so an upgrade that changes a hook
+  asks again — otherwise that reads as something breaking on its own.
+
+### Agent guidance
+
+- `memgineering-setup` gained the same detail, including where Codex records the
+  trust (`~/.codex/config.toml`). Restart your agent session after upgrading.
+
 ## [0.18.1] — 2026-08-30
 
 ### Fixed

package/assets/MEMGINEERING.md

@@ -2,7 +2,7 @@
 name: memgineering
 description: Use whenever the user refers to something they told you before, asks what was decided, tells you something worth keeping, or settles something that should hold next time. The memory lives in their own folder and outlives this session; check it before answering from guesswork, and write to it when you learn something durable.
 type: skill
-version: 0.18.1
+version: 0.18.2
 ---
 
 # memgineering

package/assets/memgineering-setup/SKILL.md

@@ -139,7 +139,12 @@ again. Two outcomes are worth recognising:
 
 The hooks go to Claude Code and Codex, and only there. Codex asks the user to
 review new hooks once at the start of the next session and runs neither until
-they answer.
+they answer — **tell them the key: `t` trusts them.** Measured on Codex
+0.149.1: both hooks show `Installed 1 / Active 0` until that panel is
+answered, and the trust is recorded per hook CONTENT
+(`[hooks.state."<path>:<event>:0:0"] trusted_hash`) in `~/.codex/config.toml`,
+so an upgrade that changes a hook asks again. Somebody who is not told this
+reads the silence as an install that did not take.
 
 Grok is the case worth knowing, because the obvious guess is wrong: it has
 hooks, more events than either of those two, and `~/.grok/hooks/` needs no

package/dist/index.js

@@ -7426,7 +7426,7 @@ function setupCommand() {
           if (choice.tools.some((t) => t.id === "codex")) {
             printHuman(
               c.gray(
-                "    \u2192 Codex will ask you to review these hooks once, next time it starts.\n      Until you answer, neither one runs."
+                "    \u2192 Codex will ask you to review these hooks once, next time it\n      starts: press `t` to trust them. Until you do, neither one runs,\n      and an upgrade that changes a hook asks again."
               )
             );
           }
@@ -7460,7 +7460,12 @@ function setupCommand() {
   Could not touch ${refused.length} file(s): ${label(refused)}`)
           );
         }
-        printHuman(c.bold("\n  Ready to use now \u2014 recall, remember and the hooks all work."));
+        const codexHooksPending = choice.hook && choice.tools.some((t) => t.id === "codex");
+        printHuman(
+          c.bold(
+            codexHooksPending ? "\n  Ready to use now \u2014 recall and remember work; the hooks start once\n  Codex has asked you about them." : "\n  Ready to use now \u2014 recall, remember and the hooks all work."
+          )
+        );
         printHuman(
           c.gray("  The guidance files just written are read at the start of a session,")
         );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memgineering",
-  "version": "0.18.1",
+  "version": "0.18.2",
   "private": false,
   "description": "One memory for the AI you connect. Recall, remember, and revise a brain your agents share \u2014 stored in your own folder.",
   "license": "Apache-2.0",