Repository navigation
MCP DevBridge 0.9.3
Windows Control diagnostics
The Windows backend status now identifies the owning registered project root. It explains that nested workspaces inherit that root's Windows Control setting, and that full filesystem/command permissions do not automatically start the optional desktop-control service. This prevents guidance that incorrectly asks users to register every nested folder as another project.
Existing Windows Control choices, the 50-tool input contract, OAuth connections, personal ChatGPT URLs, and project permission boundaries are preserved. Installing this version does not silently enable desktop control for other users. Enable Windows Control on the owning root in DevBridge when required, then restart that root after its active tasks have completed.
Compatibility
Windows, Linux/SteamOS, macOS Apple Silicon and Intel packages are built from the same source. The native Windows desktop backend is Windows-only. macOS packages remain ad-hoc signed and are not Apple notarized; this release does not add macOS in-place updating.
Verification
The owning-root regression, existing Windows bridge permission/transport suites, complete Python and Node suites, native platform builds, and package checks are included in the verification pipeline. See the attached checksums and release provenance for exact source and asset identities. QQ capture, proxy, certificate and account operations are not part of this release.