@memfork/cli 0.1.54 → 0.1.56

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.
@@ -222,13 +222,15 @@ function upsertCodexMcp(tomlPath, creds) {
222
222
  // `disabled_tools` denies the raw MemWal write tools so the agent cannot
223
223
  // bypass the on-chain DAG. All persistence is forced through `memfork commit`
224
224
  // (which writes MemWal *and* anchors on Sui). Recall + health + restore stay
225
- // enabled. Users who want raw, unanchored memory can install the standalone
226
- // MemWal plugin instead.
225
+ // enabled and are auto-approved (read-only / diagnostic no approval needed).
226
+ // Users who want raw, unanchored memory can install the standalone MemWal
227
+ // plugin instead.
227
228
  const block = `
228
229
  [mcp_servers.memwal]
229
230
  url = "${creds.relayerUrl}"
230
231
  http_headers = { Authorization = "Bearer ${creds.delegateKey}", x-memwal-account-id = "${creds.accountId}" }
231
232
  disabled_tools = ["memwal_remember", "memwal_remember_bulk", "memwal_analyze"]
233
+ default_tools_approval_mode = "auto"
232
234
  `;
233
235
  if (existing.includes("[mcp_servers.memwal]")) {
234
236
  // Replace the existing block — from the header through every following line
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@memfork/cli",
3
- "version": "0.1.54",
3
+ "version": "0.1.56",
4
4
  "description": "MemForks CLI — init, commit, recall, merge, install plugins",
5
5
  "repository": {
6
6
  "type": "git",
@@ -53,6 +53,12 @@ memfork commit \
53
53
  The CLI auto-detects the current Git branch — do **not** pass `--branch`
54
54
  unless explicitly targeting a different branch.
55
55
 
56
+ **This command performs a network write to Walrus and an on-chain transaction
57
+ on Sui. It takes 20–60 seconds to complete — this is normal.** Run it in the
58
+ foreground and wait for the `✓ Committed to <branch>` line before concluding
59
+ it succeeded or failed. Do not retry if output is slow; only retry if the
60
+ process exits with a non-zero code or prints an error.
61
+
56
62
  ### 3. Confirm to the user
57
63
 
58
64
  After the commit succeeds, print a confirmation in this form: