Windows: `jcode browser setup` fails — firefox-agent-bridge-host.exe not staged

[wolfego]

Version: jcode v0.12.1 (f6ce4fd)
OS: Windows 11 Pro 10.0.26200 (x86_64), PowerShell 5.1

After jcode browser setup:

• ~/.jcode/browser/ contains only browser.exe (918 KB) and browser-agent-bridge.xpi (25 KB)
• Setup reports: "Host binary not found at C:\Users<user>.jcode\browser\firefox-agent-bridge-host.exe"
• No native messaging host JSON manifest written
• No registry entry under HKCU\Software\Mozilla\NativeMessagingHosts or HKLM equivalent
• The v0.12.1 GitHub release assets do not include a host binary
• Firefox extension installs cleanly but reports "disconnected from native host"

jcode browser status output:
backend: firefox_agent_bridge
browser: firefox
binary: missing
setup: not complete
bridge: not responding
compatibility: extension/bridge mismatch

[1jehuang]

Fixed and verified.

Root cause was a combination of release packaging and setup repair behavior:

• firefox-agent-bridge releases shipped browser-windows-x64.exe but not the native messaging host asset (firefox-agent-bridge-host.exe / host-windows-x64.exe).
• jcode browser setup could continue after a missing host asset, considered setup complete without the host binary, and did not reliably repair the Windows native messaging registry entry when a manifest already existed.
• Windows file URL construction for extension installation also needed to use proper file:// URL conversion.

Fixes landed:

• Firefox bridge PRs:
  • Fix Windows Firefox bridge setup support firefox-agent-bridge#6 adds Windows-native host support in release assets and a Windows smoke workflow.
  • Limit bridge release workflow to supported targets firefox-agent-bridge#7 fixes the release target matrix so releases complete reliably.
• Latest bridge release is now v0.9.9 and I verified the latest-release API contains:
  • browser-windows-x64.exe
  • host-windows-x64.exe
  • browser-agent-bridge-0.9.7.xpi
• jcode master contains the browser setup fixes:
  • d4fda75 Require Firefox bridge host asset during setup
  • a68185c Use file URLs for browser extension install
  • 719b4a5 Always refresh Windows native host registry
  • 95db8ae Repair browser setup when native host is missing

Validation performed:

• Windows GitHub runner built both browser.exe and firefox-agent-bridge-host.exe successfully.
• Windows smoke test passed, including native messaging framing: it launched the host, sent a browser.exe ping, intercepted the native-message frame, injected a fake Firefox response, and verified the CLI received "pong": true.
• jcode Windows cross-target check passed on the branch containing the setup repair commits.
• Local regression test browser::browser_tests::setup_complete_requires_native_host_binary was added and passed during development.

Known scope note: persistent browser session ... mode is explicitly unsupported on Windows for now, but direct browser commands through the native messaging host are the supported path and are what jcode browser setup prepares.

[wolfego]

Thanks Jeremy, please let me know if i can assist in any way.