Multiplatform: remote host, browser client, phone shells (parked) - #175
Draft
Tryanks wants to merge 2 commits into
Draft
Multiplatform: remote host, browser client, phone shells (parked)#175Tryanks wants to merge 2 commits into
Tryanks wants to merge 2 commits into
Conversation
…dwork" This reverts commit 490aa67, reversing changes made to 2cbb089d1b90da1d68a3f6851ff0f13d7e7dae5b. Parked rather than abandoned: the remote host, the browser and phone clients, and the multiplatform CI gates all come back out of main while the work continues on its branch. Nothing here was failing — CI was green on all seven jobs when it merged. Note for whoever brings it back: re-merging the original branch will not restore these changes, because its commits remain ancestors of main through the merge this reverts. The way back is to revert *this* commit, which is what the follow-up branch does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reverts the revert in #174, restoring the remote sync host, the browser and phone clients, the shared client UI, and the multiplatform CI gates. This is the only way back. Re-merging `feat/multiplatform-groundwork` would not work: its commits remain ancestors of `main` through the merge that #174 reverted, so git treats them as already applied and the diff comes out empty. Everything here was green on all seven CI jobs before it was parked. Future work continues on this branch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Draft — parked for later. This is the multiplatform work from #173, taken back out of
mainby #174 and held here until we pick it up again.Nothing was failing. All seven CI jobs were green when #173 merged; it was parked by choice, not by defect.
Why this branch and not the original
Re-merging
feat/multiplatform-groundworkwould not work. Its commits are still ancestors ofmainthrough the merge #174 reverted, so git treats them as already applied and a PR from it shows an empty diff. Reverting the revert is the way back, which is what the single commit on this branch does.What it contains
A sync host the desktop app starts on loopback at launch, plus
tcode-serverfor machines with no display. A wire protocol (docs/sync-protocol.md) where clients send commands and the host streams events, each carrying a per-session sequence number a reconnecting client resumes from. A shared client UI compiled to wasm, Android and iOS — one implementation, three shells — that follows a session, sends turns, and answers approvals. Devices get in with a six-character pairing code, once.Four CI jobs that actually gate it. The previous workflow proved only that the desktop build worked:
client-appis outside the workspace and five other crates compile to empty shells on a host. These build them for their real targets, with no failure suppression.Known state when parked
aarch64-linux-android, all JNI entry points exported. Never run on a deviceThe mobile rows are the open question. Linking proves every symbol GPUI, wgpu, Metal, Vulkan and psm need resolves — which
cargo checkdoes not — and is still not the same as having seen a frame. The likely first failure on both is renderer creation meeting real hardware.docs/remote-and-mobile.mdis the user-facing guide;docs/multiplatform-plan.mdrecords the architecture and the approaches rejected along the way.🤖 Generated with Claude Code