Repository navigation
v0.7.3
Browser setup errors that name the problem
Windows and Linux: say who holds the browser bridge, why joining it failed, and whether the extension is installed (#36)
When an MCP server could not join the browser bridge, 0.7.2 said only that another or older server probably owned it. A missing extension, a stale server and a sandbox boundary all read the same.
Browser errors and munim-computer-use check-native-host now say:
- Whether the extension is installed. The extension id is looked up in every Chrome, Chromium, Edge and Brave profile. A missing or disabled extension is named, and installing it comes first in the next steps.
check-native-hostno longer reports "ready" while the extension is missing. - Who holds the bridge. The owning server records its pid, version, path, start time and whether the extension is connected to it. For an owner from an earlier build, which records nothing, the other munim-computer-use processes running are listed (Chrome's relay processes are left out).
- Why joining failed, from the actual connection error. Access denied means the servers run in different security contexts: a sandbox, an elevated process, or another account. No endpoint means a very old build.
- What the owner reports.
check-native-hostasks the owner directly whether the extension is connected to it, and older owners are still identified.
Also fixed: if the owner's endpoint for other servers closed, every later server was locked out of the browser until that owner exited. It now reopens.
cargo test passes on Windows and Linux; macOS is unchanged apart from the version. 32 tools; no extension update needed.