Browser Bridge extension does not support network capture; c

Error message

Browser Bridge extension does not support network capture; continuing without it. Explore output may miss API endpoints until you reload or reinstall the extension.

What it means

The Browser Bridge extension version in the connected profile does not expose the network-capture capability. Page marks network capture as unsupported, logs this one-time warning, and continues the command without capturing network traffic — meaning explore output may omit API endpoints the tool would otherwise discover from the network log. It is a capability-degradation warning, not a failure.

Source

Thrown at src/browser/page.ts:167

      }
    }
  }

  /** Get the active page identity (targetId) */
  getActivePage(): string | undefined {
    return this._page;
  }

  /** Bind this Page instance to a specific page identity (targetId). */
  setActivePage(page?: string): void {
    this._page = page;
    this._lastUrl = null;
  }
  private _markUnsupportedNetworkCapture(): void {
    this._networkCaptureUnsupported = true;
    if (this._networkCaptureWarned) return;
    this._networkCaptureWarned = true;
    log.warn(
      'Browser Bridge extension does not support network capture; continuing without it. ' +
      'Explore output may miss API endpoints until you reload or reinstall the extension.',
    );
  }

  async evaluate<T = unknown>(js: string): Promise<T>;
  async evaluate<Args extends unknown[], T>(fn: BrowserEvaluateFunction<Args, T>, ...args: Args): Promise<Awaited<T>>;
  async evaluate(input: string | BrowserEvaluateFunction<unknown[], unknown>, ...args: unknown[]): Promise<unknown> {
    const code = buildEvaluateExpression(input, args);
    try {
      return await sendCommand('exec', { code, ...this._cmdOpts() });
    } catch (err) {
      const advice = classifyBrowserError(err);
      if (advice.kind !== 'target-navigation') throw err;
      await new Promise((resolve) => setTimeout(resolve, advice.delayMs));
      return sendCommand('exec', { code, ...this._cmdOpts() });
    }
  }

View on GitHub (pinned to 49907e53dc)

Solutions

Reload the extension in chrome://extensions (toggle off/on) so it picks up the current build.
Reinstall the extension: rebuild/repackage from extension/ (or re-add from the store) in the target profile.
Confirm the extension version in chrome://extensions matches the version shipped with your installed CLI.
Ignore the warning if you don't need endpoint discovery; commands still work, only explore's API-endpoint output is affected.

Example fix

// before: stale extension loaded -> warning on explore
// after: chrome://extensions -> Browser Bridge -> Reload (or remove + reinstall), then rerun the command

Defensive patterns

Strategy: fallback

Try / catch

try {
  await startNetworkCapture(page);
} catch {
  // extension lacks capture support — proceed without network capture;
  // treat missing API endpoints in explore output as expected
}

Prevention

Keep the Browser Bridge extension updated/reloaded in every profile used by the CLI.
Reinstall the extension after upgrading the CLI so versions stay in sync.
Check chrome://extensions version against the installed CLI version when explore output looks sparse.

When it happens

Trigger: startNetworkCapture or readNetworkCapture is invoked but the extension's handshake/messaging indicates the network-capture API is absent — i.e. an older extension build is loaded in the browser profile.

Common situations: The daemon auto-updated but the unpacked/extension store build in the browser is stale; the user sideloaded an old extension zip; the extension was installed before network capture was added and never reloaded.

Related errors

AI-assisted analysis of jackwener/OpenCLI@49907e53dc (2026-08-29). Data as JSON: /api/errors/89530fdbf4fc27a1. Report an issue: GitHub.