Repository navigation
CLI: says failed to start opencode serve at first, but later generate a QR that doesnt work #128
Description
Activity
Thanks for the detailed report! The root causes are fixed in PR #130 (branch
fix/cli-tier-v2-unreachable):- 'Failed to start opencode serve' — the CLI passed
--log-level DEBUG(uppercase), which opencode v2 rejects, killing the server at startup. The CLI now detects your server major viaopencode --versionand uses the matching flags (debugon v2), health endpoint (/api/info), and/api/*proxy routes. - QR generated anyway but dead — a spawn failure only printed the error while startup continued to a scannable-but-dead QR. Spawn failures now abort immediately, and port detection only returns health-verified ports, so you'll get a clear error instead of a dead QR.
- App says 'remote server unreachable' — the app probed only
/global/health, which on v2 serves the web UI instead of JSON. It now probes/api/infofirst and caches the detected version per connection.
To try it: pull the branch (or wait for merge + release), run
npx crosscodeagain, and rescan. If your v2 binary lives under a different command, set"opencodeBin": "opencode-v2"in~/.crosscode/config.jsonorCROSSCODE_OPENCODE_BIN. If it still fails, please share the output withCROSSCODE_DEBUG=1and the last lines of~/.crosscode/crosscode.log.- 'Failed to start opencode serve' — the CLI passed
Hi there,
the Failed to start opencode serve issue with a dead QR is still present. Do I need to manually configure anything?
When launching using npx crosscode the cli at first prints:
however after a while it generates a QR code.
But still when the QR code is scanned by the mobile app it doesnt connect saying remove server is unreachable.
Also additional note, I am on starter tier using connect.crosscode.site.
Mobile app says this:
Also I am using opencode v2