@mirsella/browser-mcp 2.0.6 → 2.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.codex-plugin/plugin.json +1 -1
- package/README.md +1 -0
- package/package.json +1 -1
- package/vendor/browser-mcp +0 -0
package/README.md
CHANGED
|
@@ -264,6 +264,7 @@ action. Explicitly disabled or disconnected MCP entries stay disabled.
|
|
|
264
264
|
|
|
265
265
|
- A headed startup error mentioning `DISPLAY` or `WAYLAND_DISPLAY` means no graphical session could be found. Set `OPENCODE_BROWSER_HEADLESS=true` when running without one.
|
|
266
266
|
- A profile or socket lease error means another live package process owns it or a stale process is still running. Do not bypass the locks.
|
|
267
|
+
- If startup reports that the profile is already open in another local process, that browser may have been opened without remote debugging. Save your work, close it gracefully, and retry the MCP action. MCP will start the same profile with remote debugging enabled. To leave that browser running, use a separate `OPENCODE_BROWSER_PROFILE` or `--profile` instead. Never delete Chromium's `SingletonLock` or kill the existing browser automatically.
|
|
267
268
|
- A process on the configured CDP port must belong to the exact managed browser generation. Stop it or choose another port.
|
|
268
269
|
- If downstream startup fails, verify that `bunx` is available to OpenCode.
|
|
269
270
|
- The plugin refuses to replace an unrelated `mcp.servers.browser` entry.
|
package/package.json
CHANGED
package/vendor/browser-mcp
CHANGED
|
Binary file
|