Make zed:// links clickable in terminal - #58910
Merged
MrSubidubi merged 2 commits intoJun 9, 2026
Merged
Conversation
|
We require contributors to sign our Contributor License Agreement, and we don't have @r4victor on file. You can sign our CLA at https://zed.dev/cla. Once you've signed, post a comment here that says '@cla-bot check'. |
zed-community-bot
Bot
added
the
first contribution
Contributor
Author
|
@cla-bot check |
cla-bot
Bot
added
the
cla-signed
|
The cla-bot has been summoned, and re-checked this pull request! |
MrSubidubi
changed the title
zed:// links clickable in terminal
MrSubidubi
approved these changes
Jun 9, 2026
MrSubidubi
left a comment
MrSubidubi
left a comment
Member
There was a problem hiding this comment.
Looks good, thanks! And congrats to your first contribution! 🎉
MrSubidubi
enabled auto-merge
June 9, 2026 12:43
This was referenced Jun 18, 2026
Closed
This was referenced Jul 1, 2026
This was referenced Jul 10, 2026
jonx
pushed a commit
to jonx/zed-aros
that referenced
this pull request
Jul 17, 2026
The PR makes Zed'd own `zed://` links clickable in the Zed's integrated terminal. Previously, you had to copy and paste such links. Now you can hover and follow the link on cmd+click: <img width="794" height="354" alt="Screenshot 2026-06-09 at 15 25 18" src="https://github.com/user-attachments/assets/0c9be498-ba63-4a10-8852-cf2e23fa9597" /> </br></br> **Use case** A CLI tool can output a `zed://` link, e.g. to open a remote dev environment. If Zed's terminal makes them clickable, users can open the remote simply by clicking on the link. More specifically, [we're adding Zed support to dstack](dstackai/dstack#3947). The `dstack` CLI allows users to launch a remote dev environment with GPU. So this PR is needed to make the UX smooth: Users run the `dstack` CLI in the local terminal, the CLI prints the the `zed://` link, and the users can click the link and open a new remote Zed window. **Implementation details** `zed://` links are routed through the OS as other links and not internally. One downside is that dev builds may open an installed Zed version. Made this tradeoff to keep the diff simple. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content adheres to Zed's UI standards ([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) and [icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md) guidelines) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Release Notes: - Made `zed://` links clickable in the terminal
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
2 participants
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 PR makes Zed'd own
zed://links clickable in the Zed's integrated terminal. Previously, you had to copy and paste such links. Now you can hover and follow the link on cmd+click:Use case
A CLI tool can output a
zed://link, e.g. to open a remote dev environment. If Zed's terminal makes them clickable, users can open the remote simply by clicking on the link.More specifically, we're adding Zed support to dstack. The
dstackCLI allows users to launch a remote dev environment with GPU. So this PR is needed to make the UX smooth: Users run thedstackCLI in the local terminal, the CLI prints the thezed://link, and the users can click the link and open a new remote Zed window.Implementation details
zed://links are routed through the OS as other links and not internally. One downside is that dev builds may open an installed Zed version. Made this tradeoff to keep the diff simple.Self-Review Checklist:
Release Notes:
zed://links clickable in the terminal