feat: connect managed MCP clients through independent Nova.app - #39
Conversation
|
Independent agent review completed for exact head No blocking finding introduced by the diff or required for #33's acceptance slice. The reviewer traced macOS's early pure-connector return, non-macOS stdio, manifest compatibility, ongoing streaming, independent service lifetime and the explicit source/release/TCC limits in documentation. Independent local verification: 3 CLI tests and 3 managed transport tests passed. Additional real-process fixture probes passed for simultaneous connectors, keeping the second usable after the first exits, and insecure-runtime-directory rejection with clean MCP stdout. Current exact-head CI: all six jobs passed in https://github.com/bigduu/Nova/actions/runs/33946225704, including the existing macOS app-service/stdio suite and the new native Linux managed-stdio test. The pre-existing connector EOF / blocking stdin lifetime issue was reproduced through both the new entrypoint and unchanged |
Summary
The Nova plugin previously ran desktop APIs directly in Bamboo/Bodhi's process chain on macOS. It now runs
nova mcp: macOS connects to the independently installed Nova.app before any desktop initialization or permission request; Windows and Linux retain the existing stdio server.An unavailable app fails with installation and Nova-only reconnection guidance instead of falling back to host-owned desktop APIs. Existing direct CLI,
--connect, HTTP, and the optional Chrome DevTools launcher remain compatible. Documentation explains independent app installation, keeping Bodhi open during reconnection, and the remaining signed-release/TCC upgrade acceptance gates. The published v0.2.1 release is unchanged and predates this entrypoint.Closes #33. Part of bigduu/Zenith#185.
Test Plan
Screenshots
Not applicable: this slice changes CLI/plugin routing and documentation; no graphical UI is changed.