@memfork/cli 0.1.55 → 0.1.57

package/dist/commands/install.js

@@ -201,7 +201,7 @@ network_access = true
     console.log("");
     console.log(tip("The agent now has:"));
     console.log(dim("    memwal_recall          — semantic memory recall via MemWal MCP"));
-    console.log(dim("    memfork commit / merge — the only write path: MemWal + on-chain anchor"));
+    console.log(dim("    memfork commit / merge — the only write path: Walrus blob + branch tracking"));
     console.log("");
     console.log(dim("    Raw MemWal writes (remember / remember_bulk / analyze) are disabled"));
     console.log(dim("    so every saved memory is anchored on Sui. Want raw, unanchored notes?"));
@@ -221,7 +221,9 @@ function upsertCodexMcp(tomlPath, creds) {
     }
     // `disabled_tools` denies the raw MemWal write tools so the agent cannot
     // bypass the on-chain DAG. All persistence is forced through `memfork commit`
-    // (which writes MemWal *and* anchors on Sui). Recall + health + restore stay
+    // (which writes to Walrus via MemWal — no Sui tx per commit; on-chain events
+    // only happen on branch creation and merge settlement). Recall + health +
+    // restore stay
     // enabled and are auto-approved (read-only / diagnostic — no approval needed).
     // Users who want raw, unanchored memory can install the standalone MemWal
     // plugin instead.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memfork/cli",
-  "version": "0.1.55",
+  "version": "0.1.57",
   "description": "MemForks CLI — init, commit, recall, merge, install plugins",
   "repository": {
     "type": "git",

package/plugins/codex/plugins/memforks/skills/memory-commit/SKILL.md

@@ -53,6 +53,12 @@ memfork commit \
 The CLI auto-detects the current Git branch — do **not** pass `--branch`
 unless explicitly targeting a different branch.
 
+**This command writes to Walrus via the MemWal relayer. It takes 20–60 seconds
+to complete — this is normal network latency, not a hang.** Run it in the
+foreground and wait for the `✓ Committed to <branch>` line before concluding
+it succeeded or failed. Do not retry if output is slow; only retry if the
+process exits with a non-zero code or prints an error.
+
 ### 3. Confirm to the user
 
 After the commit succeeds, print a confirmation in this form: