Richard Feldman
513e2b2ee3
[PR #57878](https://github.com/zed-industries/zed/pull/57878) introduced a per-thread sandboxing temp directory that, for every terminal command, overrode `TMPDIR`/`TMP`/`TEMP` and pushed the directory into the sandbox writable scope. For remote projects this temp directory is created on the client while the terminal actually runs on the remote host, so it leaked client-side environment variables into the remote terminal and pointed `$TMPDIR` at a path that doesn't exist there. This gates the temp-directory logic behind `project.is_local()`, so remote projects no longer get their terminal environment infected. This doesn't restore the per-thread tempdir behavior for remoting, but it undoes the regression. Closes AI-348 Release Notes: - Fixed remote terminals having their environment overridden by client-side temp directory variables
Zed
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:
- Web (tracking discussion)
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 specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor 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 theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/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.