fix: Keep gmgui process alive to maintain server uptime

When running via bunx, gmgui was exiting after the server started,
causing the entire application to close. Now gmgui stays alive
indefinitely, keeping the server running. This allows 'bunx agentgui'
to work properly without closing immediately.

Author: lanmower

bin/gmgui.cjs

@@ -21,9 +21,12 @@ async function gmgui(args = []) {
     const useBun = hasBun();
     const installer = useBun ? 'bun' : 'npm';
 
-    // Ensure dependencies are installed
+    // Ensure dependencies are installed only if node_modules is missing
+    // Skip this for bunx which manages dependencies independently
     const nodeModulesPath = path.join(projectRoot, 'node_modules');
-    if (!fs.existsSync(nodeModulesPath)) {
+    const isBunx = process.env.npm_execpath && process.env.npm_execpath.includes('bunx');
+
+    if (!isBunx && !fs.existsSync(nodeModulesPath)) {
       console.log(`Installing dependencies with ${installer}...`);
       const installResult = spawnSync(installer, ['install'], {
         cwd: projectRoot,
@@ -45,12 +48,17 @@ async function gmgui(args = []) {
         stdio: 'inherit'
       });
 
+      ps.on('error', reject);
+
+      // Keep this process alive indefinitely to keep the server running
+      // The server will handle all actual work; this process just provides the bridge
+      process.stdin.resume();
+
+      // If server exits unexpectedly, log it but keep trying
       ps.on('exit', (code) => {
-        if (code === 0) resolve();
-        else reject(new Error(`Server exited with code ${code}`));
+        console.error(`Server process exited with code ${code}`);
+        // Don't reject or resolve - just keep waiting
       });
-
-      ps.on('error', reject);
     });
   } else {
     throw new Error(`Unknown command: ${command}`);