Fix #43 (#45) Fix macOS single-instance port collision with Zed#45
Merged
Merged
Conversation
Open
naaiyy
approved these changes
Apr 6, 2026
naaiyy
left a comment
There was a problem hiding this comment.
Good to merge. I'll make a small cleanup follow-up for the inherited Zed naming in a separate PR.
Open
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.
Context
Fixes #43
Glass inherited Zed's macOS single-instance port range (base 43737) and handshake check. Both apps bind the same per-channel localhost port on startup to enforce "only one instance running." When Zed already holds that port, Glass sees the handshake, concludes it is already running, and exits immediately (and vice versa) a.k.a crashes.
This changes Glass to use its own base port (44737) so the two apps no longer collide.
How to Review
One file:
crates/zed/src/zed/mac_only_instance.rs. The only functional change is the port base constant and the four match arms that reference it. The comment block above the match was updated to reflect the new example port numbers.Self-Review Checklist
Release Notes: