BrowserDebug v1.2.0
BrowserDebug v1.2.0 Release Notes
One MCP, Multiple Explicit Projects
BrowserDebug v1.2.0 adds --registry mode. A single Codex or other MCP-host configuration can now discover and select projects already registered in the local BrowserDebug Console.
The MCP exposes only path-free logical project IDs. It cannot add/remove registry entries, accept an arbitrary target path, read arbitrary files, or bypass existing confirmation and ownership boundaries.
Public Interface
- New
browserdebug_list_projectsread-only tool. - Optional
projectIdon project-specific tools; required in registry mode and backward-compatible in single-target mode. - New project and project-run resources.
- MCP manifest schema v2, with the historical v1 schema retained as a read-only resource.
Compatibility
Existing --root <target> [--config <relative-config>] configurations continue to work without adding projectId. Registry mode is opt-in through --registry.
Validation
The release includes official MCP SDK client coverage for both single-target mode and one registry-mode server running two separately registered temporary projects. Full release-gate results are recorded in ACCEPTANCE.md.