venombrowser 4.1.0 → 4.1.1

package/bin/venombrowser-agent.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * VenomBrowser Agent — CLI entry point (Kimi-style)
  *

package/bin/venombrowser-chat.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * VenomBrowser Interactive Chat Agent — CLI entry point (Kimi-style)
  *

package/bin/venombrowser-cli.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * VenomBrowser CLI — Unified command dispatcher
  *

package/bin/venombrowser-mcp.js

@@ -1,30 +1,148 @@
-#!/usr/bin/env node
-/**
- * VenomBrowser MCP Server — CLI entry point
- * Starts the MCP server in stdio mode for agent integration.
- *
- * Usage: node bin/venombrowser-mcp.js
- * Or:    npm run mcp
- *
- * Agent configuration example (Claude Code):
- *   {
- *     "mcpServers": {
- *       "venombrowser": {
- *         "command": "node",
- *         "args": ["C:/path/to/VenomBrowser/server/bin/venombrowser-mcp.js"],
- *         "env": { "REST_API_KEY": "your-bridge-api-key" }
- *       }
- *     }
- *   }
- */
-
-// Load .env for default config — agents can also pass env vars directly
-require('dotenv').config({ path: require('path').join(__dirname, '..', '.env') });
-
-const VenomBrowserMcpServer = require('../src/mcp-server');
-
-const server = new VenomBrowserMcpServer();
-server.start().catch(err => {
-  console.error('[VenomBrowser MCP] Failed to start:', err.message);
-  process.exit(1);
-});
+#!/usr/bin/env node
+/**
+ * VenomBrowser MCP Server — CLI entry point
+ * Starts the MCP server in stdio mode for agent integration.
+ *
+ * Kimi-style: Auto-starts the bridge daemon if it's not already running.
+ * The agent just configures this MCP entry — no manual `venombrowser start` needed.
+ *
+ * Usage: node bin/venombrowser-mcp.js
+ * Or:    npm run mcp
+ *
+ * Agent configuration example (Claude Code / Cursor):
+ *   {
+ *     "mcpServers": {
+ *       "venombrowser": {
+ *         "command": "venombrowser-mcp",
+ *         "env": { "BRIDGE_PORT": "10086" }
+ *       }
+ *     }
+ *   }
+ *
+ * Agent configuration example (OpenCode):
+ *   {
+ *     "mcp": {
+ *       "venombrowser": {
+ *         "type": "local",
+ *         "command": ["venombrowser-mcp"],
+ *         "environment": { "BRIDGE_PORT": "10086" }
+ *       }
+ *     }
+ *   }
+ */
+
+// Load .env for default config — agents can also pass env vars directly
+require('dotenv').config({ path: require('path').join(__dirname, '..', '.env') });
+
+const path = require('path');
+const http = require('http');
+const { spawn } = require('child_process');
+const fs = require('fs');
+
+const BRIDGE_PORT = parseInt(process.env.BRIDGE_PORT || '10086', 10);
+const BRIDGE_HOST = process.env.BRIDGE_HOST || '127.0.0.1';
+const MAX_WAIT_ATTEMPTS = 30;       // 30 × 500ms = 15 seconds max wait
+const POLL_INTERVAL_MS = 500;
+
+// ─── Health check ─────────────────────────────────────────────────────────
+function checkBridgeHealth() {
+  return new Promise((resolve) => {
+    const req = http.get(
+      `http://${BRIDGE_HOST}:${BRIDGE_PORT}/health`,
+      { timeout: 2000 },
+      (res) => {
+        let body = '';
+        res.on('data', (chunk) => { body += chunk; });
+        res.on('end', () => {
+          try {
+            const data = JSON.parse(body);
+            resolve(data.server === 'ok');
+          } catch {
+            resolve(false);
+          }
+        });
+      }
+    );
+    req.on('error', () => resolve(false));
+    req.on('timeout', () => { req.destroy(); resolve(false); });
+  });
+}
+
+// ─── Wait for bridge to become ready ──────────────────────────────────────
+function sleep(ms) {
+  return new Promise((resolve) => setTimeout(resolve, ms));
+}
+
+async function waitForBridge() {
+  for (let i = 0; i < MAX_WAIT_ATTEMPTS; i++) {
+    if (await checkBridgeHealth()) return true;
+    await sleep(POLL_INTERVAL_MS);
+  }
+  return false;
+}
+
+// ─── Auto-start the bridge daemon ─────────────────────────────────────────
+async function ensureBridgeRunning() {
+  // Already running? Great, nothing to do.
+  if (await checkBridgeHealth()) {
+    console.error('[VenomBrowser MCP] Bridge daemon already running on port ' + BRIDGE_PORT);
+    return true;
+  }
+
+  console.error('[VenomBrowser MCP] Bridge daemon not running — auto-starting...');
+
+  const serverScript = path.join(__dirname, 'venombrowser-server.js');
+  const serverCwd = path.join(__dirname, '..');
+
+  // Create a log file for the daemon's output
+  const logDir = path.join(serverCwd, 'logs');
+  if (!fs.existsSync(logDir)) fs.mkdirSync(logDir, { recursive: true });
+  const logFile = path.join(logDir, 'bridge-daemon.log');
+
+  // Spawn the bridge server as a fully detached background process.
+  // This means: when the MCP process exits, the bridge stays alive.
+  // The bridge maintains the WebSocket connection with the Chrome extension.
+  const logFd = fs.openSync(logFile, 'a');
+  const child = spawn(process.execPath, [serverScript], {
+    detached: true,
+    stdio: ['ignore', logFd, logFd],
+    env: { ...process.env },
+    cwd: serverCwd,
+    windowsHide: true
+  });
+
+  // Unref so the MCP process can exit independently
+  child.unref();
+
+  console.error(`[VenomBrowser MCP] Spawned bridge daemon (PID ${child.pid}), waiting for ready...`);
+  console.error(`[VenomBrowser MCP] Daemon logs: ${logFile}`);
+
+  // Wait for the bridge to be ready
+  const ready = await waitForBridge();
+
+  if (ready) {
+    console.error('[VenomBrowser MCP] Bridge daemon is ready!');
+    return true;
+  } else {
+    console.error('[VenomBrowser MCP] WARNING: Bridge daemon did not become ready within 15s.');
+    console.error('[VenomBrowser MCP] Check logs at: ' + logFile);
+    console.error('[VenomBrowser MCP] Continuing anyway — commands will fail if daemon is not running.');
+    return false;
+  }
+}
+
+// ─── Main ─────────────────────────────────────────────────────────────────
+async function main() {
+  // Step 1: Ensure the bridge daemon is running (Kimi-style auto-start)
+  await ensureBridgeRunning();
+
+  // Step 2: Start the MCP server (stdio transport for agent communication)
+  const VenomBrowserMcpServer = require('../src/mcp-server');
+  const server = new VenomBrowserMcpServer();
+  await server.start();
+}
+
+main().catch(err => {
+  console.error('[VenomBrowser MCP] Failed to start:', err.message);
+  process.exit(1);
+});

package/bin/venombrowser-server.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * VenomBrowser Bridge Server — CLI entry point
  * Starts the WebSocket + REST API bridge server.

package/bin/venombrowser-setup.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 /**
  * VenomBrowser Setup — Interactive setup wizard
  *
@@ -149,9 +149,9 @@ async function main() {
   console.log('🚀 Next steps:');
   if (!final.WS_AUTH_TOKEN || final.WS_AUTH_TOKEN.includes('paste')) {
     console.log('   1. Set your WS_AUTH_TOKEN (see instructions above)');
-    console.log('   2. venombrowser start     — start the bridge server');
+    console.log('   2. Start using your AI agent (the bridge daemon will auto-start)');
   } else {
-    console.log('   1. venombrowser start     — start the bridge server');
+    console.log('   1. Start using your AI agent (the bridge daemon will auto-start)');
   }
   console.log('   2. venombrowser chat      — start interactive chat');
   console.log('   3. venombrowser agent "task" — run a one-shot task');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "venombrowser",
-  "version": "4.1.0",
+  "version": "4.1.1",
   "description": "Agent-agnostic browser automation platform — give any AI agent eyes and hands in your real Chrome browser",
   "author": "TechVenom",
   "main": "src/bridge-server.js",