Repository navigation
feat(cli,tunnel-server): BYO tunnel setup UX + tunnel connection robustness fixes - #152
Merged
Merged
Conversation
added 9 commits
October 19, 2026 11:33
…ad sockets, quiet late-chunk spam
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two workstreams in one branch:
1. BYO tunnel setup UX (\packages/crosscode)
\1. CrossCode Tunnel (recommended) 2. Cloudflared Named 3. Cloudflared Quick 4. Ngrok\ — each with live installed/not-found status, default 1.
2. Tunnel-server robustness (\packages/tunnel-server, bumped to 0.2.4)
Diagnosis notes (from prod docker logs)
The live tunnel proxies fine (200s across /api/info, /global/health, /session, \POST /session). The \Tunnel not active\ lines are all stale project IDs polled by stored app connections (other project dir, pre-entropy 8-char IDs incl. another machine's, and the pre-switch \e816…\ URL). Remaining user-side issues are environmental: cloudflared binary missing on the test box, empty
grok.log\ (ngrok never served), and expired/insufficient-funds opencode provider keys. App-side stale-connection rebind is a mobile follow-up, not in this PR.
Test plan