[Bug]: Windows "Open in Zed" opens Zed Nightly instead of stable Zed

Open Beginner friendly
#1,978 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop, devtools

Research direction

Start in apps/server and trace how the Zed editor choice resolves the zed and zeditor commands on Windows. Reproduce with stable Zed and Zed Nightly installed and both commands on PATH; done means choosing Zed, including the shortcut, opens the stable installation without requiring PATH changes.

Written by the indexing model from the issue text.

Description

bug needs-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Use T3 Code on Windows with both stable Zed and Zed Nightly installed.
  2. Ensure both zed and zeditor are available on PATH.
  3. Open a project/thread in T3 Code.
  4. Click Open and choose Zed, or use the preferred-editor shortcut when Zed is selected.
Expected behavior

Choosing Zed should open the stable Zed install.

Actual behavior

T3 Code resolves the zed command first and opens Zed Nightly instead of stable Zed.

Impact

Minor bug or occasional failure

Version or commit

main @ 0.017

Environment

Windows, T3 Code, Zed stable and Zed Nightly both installed.

Logs or stack traces
Screenshots, recordings, or supporting files

No response

Workaround

Uninstall Zed Nightly, remove its command from PATH, or reorder PATH so the stable command resolves first.

Dominant language
TypeScript
Stars
23.2k
Forks
5.9k
Avg merge
10h 57m
Merged PRs (30d)
365

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.