@mirsella/browser-mcp 2.0.5 → 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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "browser",
3
- "version": "2.0.5",
3
+ "version": "2.0.7",
4
4
  "description": "Shared Chromium profile with isolated conversation tabs for Codex and OpenCode.",
5
5
  "author": {
6
6
  "name": "mirsella"
package/README.md CHANGED
@@ -77,7 +77,9 @@ The broker writes diagnostics to
77
77
  prints the exact path. Logs are readable only by your user and also go to stderr.
78
78
 
79
79
  Request tracing records the tool name, session ID, current stage, and elapsed
80
- time. It does not record tool arguments. If a call stalls, look for its last
80
+ time. Chrome DevTools worker stderr is drained into that private broker log,
81
+ so replacement workers survive a disconnected host's stderr. Request tracing
82
+ does not record tool arguments. If a call stalls, look for its last
81
83
  stage and whether the broker recorded a deadline, cancellation, catalog failure,
82
84
  or worker replacement. Browser stderr is captured in
83
85
  `browser-<profile-hash>.log` in the same directory. Its separate writer survives
@@ -262,6 +264,7 @@ action. Explicitly disabled or disconnected MCP entries stay disabled.
262
264
 
263
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.
264
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.
265
268
  - A process on the configured CDP port must belong to the exact managed browser generation. Stop it or choose another port.
266
269
  - If downstream startup fails, verify that `bunx` is available to OpenCode.
267
270
  - The plugin refuses to replace an unrelated `mcp.servers.browser` entry.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mirsella/browser-mcp",
3
- "version": "2.0.5",
3
+ "version": "2.0.7",
4
4
  "description": "Session-isolated browser automation over MCP and Chrome DevTools Protocol",
5
5
  "type": "module",
6
6
  "exports": {
Binary file