Repository navigation
fix(desktop): connect to the server already using the T3 home - #165
Merged
Merged
Conversation
|
ScriptedAlchemy
enabled auto-merge
November 19, 2026 06:59
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.
Opening Desktop after an SSH connection started a standalone server against the same T3 home made Desktop quit with “This T3 home is unavailable.” On a Linux Spark running Nightly .211, that server was healthy and serving the original environment.
Desktop now uses the existing server when it proves ownership of the same unmanaged home. Desktop issues a scoped session through its bundled CLI and verifies the environment ID, port and fresh challenge over loopback before exposing the session to the renderer. This also handles a server winning the lock during startup. Desktop leaves the external process running on quit and revokes its own session. Sharing settings reflect which process controls the listener.
Verified with two native Electron launches against an isolated standalone .211 server. Desktop opened the seeded project and its authenticated session returned HTTP 200. The same server PID still served discovery after quit, and the desktop session was revoked. The wrong environment ID failed verification. The second launch also verified the sharing settings against a loopback-only server.
The changed-file gate passed with 62 tests and type checks across 38 affected packages.
Implemented and tested with GPT-6 in Codex Desktop.