memex-mvp 0.10.8 → 0.10.9

package/lib/cli/index.js

@@ -1707,7 +1707,10 @@ Examples:
   memex web --port 9000                  custom port
   memex web --public --token s3cret      bind on 0.0.0.0 with bearer auth
 `);
-      return;
+      // Help path: exit cleanly so the caller (server.js) doesn't fall through
+      // to MCP-mode init, and Node doesn't warn about an unsettled top-level
+      // await waiting on an HTTP server that was never started.
+      process.exit(0);
     }
     else if (a.startsWith('--')) {
       console.error(`Unknown flag: ${a}`);
@@ -1734,7 +1737,12 @@ Examples:
 
   const { startServer } = await import('../web/index.js');
   await startServer(opts);
-  // startServer keeps the process alive on its own http server.
+  // The HTTP server now holds the event loop open. Park on an unsettled
+  // promise so cmdWeb never returns to the dispatcher — that way server.js
+  // doesn't reach process.exit(0) below or fall through to MCP-mode init.
+  // (Required because `await runCli(...)` would otherwise resolve as soon
+  // as startServer's listen-callback fires.)
+  await new Promise(() => {});
 }
 
 // =============================================================

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memex-mvp",
-  "version": "0.10.8",
+  "version": "0.10.9",
   "description": "Local-first MCP server for cross-agent AI memory. One SQLite + FTS5 corpus across Claude Code, Cowork, Cursor, Continue, Zed, Obsidian, and Telegram — passively captured, verbatim, searchable from any MCP-compatible client.",
   "type": "module",
   "main": "server.js",

package/server.js

@@ -64,31 +64,23 @@ import { runCli, CLI_SUBCOMMAND_NAMES } from './lib/cli/index.js';
 //
 // This runs BEFORE any DB/watcher side-effects so the CLI doesn't open
 // the DB in write mode unnecessarily.
-// We use a labelled async IIFE so we can `break` (or just fall through)
-// without abusing top-level `return`, which is illegal in ESM modules.
 {
   const sub = process.argv[2];
   if (sub && CLI_SUBCOMMAND_NAMES.includes(sub)) {
+    // For long-running subs (currently only `web`), cmdWeb parks on an
+    // unsettled promise after starting the HTTP server, so this `await`
+    // never resolves and process.exit below is never reached. For one-shot
+    // subs (search, recent, telegram, …), runCli returns and we exit here.
     await runCli(sub, process.argv.slice(3));
-    // 'web' is a long-running server — exiting here would kill it the moment
-    // startServer's listen-callback resolves. Let the HTTP server hold the
-    // event loop open instead.
-    if (sub !== 'web') process.exit(0);
-  } else if (sub && !sub.startsWith('-')) {
+    process.exit(0);
+  }
+  if (sub && !sub.startsWith('-')) {
     // Unknown positional subcommand — fail fast with help, don't drift
     // into MCP mode (which would just hang waiting for stdin).
     console.error(`Unknown subcommand: ${sub}`);
     console.error(`Run 'memex --help' for usage.`);
     process.exit(2);
   }
-  // For 'web': fall through to the rest of server.js so it keeps running.
-  // Actually no — the rest of server.js initializes MCP mode (stdin handler,
-  // DB watchers). For 'web' we DON'T want that. Sentinel-exit instead:
-  if (sub === 'web') {
-    // Server is listening — nothing more for this process to do.
-    // Just sit on the event loop until the HTTP server is closed.
-    await new Promise(() => {});
-  }
   // No args (or only flags we don't recognize) → MCP mode
 }