- Rust 95.2%
- JSON-with-Comments 2.5%
- Python 0.8%
- Inno Setup 0.3%
- Tree-sitter Query 0.3%
- Other 0.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
- Move `AcpConnection`, its defaults, the v1 builder/capabilities/wire handlers, legacy session/config/MCP operations and session-list implementation into `acp/v1.rs` alongside `acp/v2.rs`. - Keep foreground routing/context, shared session/config data, v2 client ingress, canonical permission/elicitation application, shared terminal-auth construction and error/lifecycle helpers in the root/shared modules. - Keep only the v1 config-setting wire method on the shared config data in `v1.rs`; the shared constructor/state stays in the root. The existing mixed session record is not redesigned in this extraction. - Preserve public paths through root reexports (`AcpConnection`, `AcpSessionList`, `connect`, the Gemini terminal-auth constant and conditional `test_support`). Consumer call sites are unchanged. The shared-runtime test imports the moved private v1 driver directly. - Keep compatibility/ingress tests alongside the legacy harness they exercise; v2 connection/auth tests stay in `v2.rs`. Test names gain the v1 module prefix but their bodies and scheduler behavior are unchanged. ## Review This is a large source relocation, not thousands of new implementation lines. For copy-aware review: ```sh git diff -B -M origin/main...HEAD -- crates/agent_servers/src/acp.rs crates/agent_servers/src/acp/v1.rs crates/agent_servers/src/acp/runtime.rs ``` Git recognizes `v1.rs` as a 93%-similar copy of the old adapter. Review the retained root boundary and the small import/visibility changes rather than re-reviewing unchanged test bodies. Release Notes: - N/A |
||
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .wezel | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| corgi.toml | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| Procfile | ||
| Procfile.web | ||
| README.md | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
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.