feat: support standalone browser mode overrides#41
Open
0xsline wants to merge 1 commit intojackwener:mainfrom
Open
feat: support standalone browser mode overrides#410xsline wants to merge 1 commit intojackwener:mainfrom
0xsline wants to merge 1 commit intojackwener:mainfrom
Conversation
Owner
|
It is currently supported, please refer to the latest documentation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OPENCLI_BROWSER_MODE=extension|standaloneto override the default browser mode selectionOPENCLI_MCP_NO_SANDBOX=1support for Linux root / VPS Chromium runsWhy
Today
buildMcpArgs()always forces--extensionoutside 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 timeoutwhen no MCP browser extension was present--no-sandboxwas passedThis change keeps the current defaults intact, but adds an explicit escape hatch for standalone environments.
Testing
npm test -- src/browser.test.tsnpm run build