Repository navigation
feat(client): use the FTW Cloud tunnel without relay fallback - #95
Merged
Merged
Conversation
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ftw-webapp | 9dea374 | Commit Preview URL Branch Preview URL |
Oct 17 2026, 06:05 AM |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
This was referenced Oct 17, 2026
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
1 participant
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.
The web client still uses the Frankfurt relay while iPhone reaches its box through FTW Cloud. This change puts the web client's existing box session inside the same Cloud
tunprotocol, over WebSocket.A current QR supplies the Cloud home id. Existing web users pair again; there is no migration bridge or relay fallback. The public bundle and CSP permit only FTW Cloud for the box connection. Passkeys keep the
app.ftw.energyRP ID.The outer Noise session authenticates FTW Cloud with its pinned service key. The inner Noise session still ends at the box: API reads, history and commands keep their existing handlers and checks. The readable copy can stay off. Pairing explains the stable home id, addresses and timing visible to Cloud. Its envelopes never enter UI state. A Web Lock gives a home one connection across visible tabs; a hidden tab releases it. Reconnects use fresh session ids and do not replay commands. Recovery blobs carry the home id, remain 512 bytes, and use format 3. Old copies require a fresh QR.
Paired Core change: srcfl/ftw#1683 enables QR v3 for linked boxes. Ship that Core release before publishing this client. The wire and registry do not change. This follows the decision on srcfl/ftw#1632; #87 stays paused.
Validation:
npm run checkpassed. All 1,126 enabled tests passed (npm test -- --maxWorkers=2 --testTimeout=15000); the longer runner timeout lets the existing bucket timing test finish on this Mac. Two opt-in tests skip by default.npm run buildpassed.ftwclouddat b2448d2 and Core with its relay unreachable: the shipped pairing/connect stack streamed, confirmed 30 commands and resumed five times. No physical hardware was used.This does not deploy either app or stop Frankfurt. Core's old relay socket, iPhone's fallback, relay dead-man notifications and fleet collection still need the retirement step. Browser Cloud push, reading the optional Cloud copy, WebTransport and escrow hosting remain separate work.