Skip to content

feat: support standalone browser mode overrides#41

Open
0xsline wants to merge 1 commit intojackwener:mainfrom
0xsline:fix/browser-mode-vps
Open

feat: support standalone browser mode overrides#41
0xsline wants to merge 1 commit intojackwener:mainfrom
0xsline:fix/browser-mode-vps

Conversation

@0xsline
Copy link

@0xsline 0xsline commented Mar 17, 2026

Summary

  • add OPENCLI_BROWSER_MODE=extension|standalone to override the default browser mode selection
  • add OPENCLI_MCP_NO_SANDBOX=1 support for Linux root / VPS Chromium runs
  • document the new VPS / CI flow in the README and testing docs

Why

Today buildMcpArgs() always forces --extension outside CI. That works well on a local machine with the Playwright MCP Bridge extension, but it makes VPS and headless Linux setups awkward even when Chromium is already installed.

I hit two concrete issues while testing on a Debian VPS:

  • Extension connection timeout when no MCP browser extension was present
  • Chromium launch failures as root unless --no-sandbox was passed

This change keeps the current defaults intact, but adds an explicit escape hatch for standalone environments.

Testing

  • npm test -- src/browser.test.ts
  • npm run build

@jackwener
Copy link
Owner

It is currently supported, please refer to the latest documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants