Xin Zhao 5504e87bfd workspace: Fix trust scope paths when connecting to Windows hosts from Unix (#63102)
# Objective

This is another fix related to the path handling issue when connecting
from Unix to Windows, similar to #62038 and #63075, but confined to the
path handling in the security modal. The root cause is the same: when
using the standard library `Path` API across platforms — especially
connecting from Unix to Windows — these `Path` methods give wrong
results.

The bugs I have observed include:
1. When opening a single file, its parent folder is not shown properly
in the project list.
2. When opening a folder, no parent folder is auto-filled into the input
field after "Trust all projects in".
3. When Zed runs in debug mode, opening two untrusted folders, checking
"Trust parents", and then trusting would result in a panic.

## Solution

Use the corresponding methods in `PathStyle`, which is designed for
handling paths across platforms, instead of the `Path` methods in the
relevant code.

## Testing

Built and tested locally, with comparison screenshots attached.

## 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)
- [ ] Tests cover the new/changed behavior
- [x] Performance impact has been considered and is acceptable

## Showcase

|| Before | After |
|:--:|:--:|:--:|
| Auto fill |<img width="657" height="343" alt="auto_fill_before"
src="https://github.com/user-attachments/assets/e36ca3d5-998c-4bed-94e9-f97dd0e7ebf4"
/>| <img width="654" height="333" alt="auto_fill_after"
src="https://github.com/user-attachments/assets/c8413fb5-d2dd-427a-afb0-9cbebc033742"
/> |
| Single file | <img width="654" height="322" alt="single_file_before"
src="https://github.com/user-attachments/assets/bfe87ab0-bf87-491a-8f85-b5a2681763a9"
/>| <img width="657" height="325" alt="single_file_after"
src="https://github.com/user-attachments/assets/0437cbde-42c3-44f6-847b-abd33e54cd2c"
/> |

---

Release Notes:

- Fixed trusting projects on remote Windows machines from Unix systems
2026-10-16 11:32:38 +00:00
…
…
…
…
…
…
…
…
…
…
…
…

Zed

Zed CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Sponsorship

Zed is developed by Zed Industries, Inc., a for-profit company.

If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.

S
Description
No description provided
Readme 1.7 GiB
Languages
Rust 95.4%
JSON-with-Comments 2.4%
Python 0.8%
Inno Setup 0.3%
Tree-sitter Query 0.3%
Other 0.3%