@memfork/cli 0.1.53 → 0.1.54

package/dist/cli.js

@@ -182,9 +182,29 @@ program.parseAsync(process.argv).catch((e) => {
     process.exit(1);
 });
 // ─── Helpers ──────────────────────────────────────────────────────────────────
+/**
+ * Flush stdout/stderr, then exit with `code`.
+ *
+ * Commands like `commit` open keep-alive sockets to the relayer / Sui RPC that
+ * hold Node's event loop open long after the work is done — so the process
+ * would otherwise hang for ~minutes instead of returning. Agents (Codex) read
+ * this as a stuck command and retry, producing duplicate commits. We exit
+ * explicitly once the command resolves.
+ *
+ * We can't use a bare `process.exit()` because it truncates buffered output
+ * when stdout is a pipe (which it always is under an agent). Writing an empty
+ * chunk with a callback guarantees the prior writes have drained first.
+ */
+function flushAndExit(code) {
+    let pending = 2;
+    const done = () => { if (--pending === 0)
+        process.exit(code); };
+    process.stdout.write("", done);
+    process.stderr.write("", done);
+}
 function wrap(fn) {
     return (...args) => {
-        fn(...args).catch((e) => {
+        fn(...args).then(() => flushAndExit(0), (e) => {
             if (e.name === "ConfigError") {
                 console.error(chalk.red("\n  " + String(e.message)));
                 console.error(chalk.cyan("  → Run `memfork init` to configure.\n"));
@@ -192,7 +212,7 @@ function wrap(fn) {
             else {
                 console.error(chalk.red("\nError: " + String(e)));
             }
-            process.exit(1);
+            flushAndExit(1);
         });
     };
 }

package/package.json

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