mirror of
https://github.com/zed-industries/zed.git
synced 2026-10-28 18:24:54 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
2e794a1ea7
Stacked on #66252. This is the first of three steps that move native subagents onto the ACP subagent path. Native cards look the same after this PR. What changes is where their status can come from, which step 2 needs once `spawn_agent` stops showing a tool call. **Association.** Native subagent sessions now get a `SubagentAssociation`, like ACP subagents: the label is its title, and cancel is allowed. A reloaded subagent gets one too. **Outcomes.** A native run already reports `running` and `idle`, but its idle state only says how the model stopped. When a `spawn_agent` run ends, `NativeSubagentHandle::send` now reports the run's verdict as another idle state, with the same stop reason and error text that the tool call gets: - A run stopped near the context limit reports a failure with that message, not `cancelled`. The handle now also waits for the run to finish before reporting. - A run that ends without a reply reports a failure. - An idle report with no entries since the previous one now restates that outcome instead of adding another. This also applies to ACP subagents. **Saved and restored.** Each outcome is saved in the subagent's `SubagentContext`, with the transcript length when the run ended. It's skipped when empty, so threads without outcomes save exactly as before. After `open_thread` replays a subagent, the native agent restores its outcomes. The last one becomes the current state unless entries followed it, as when Zed quit mid-run. **Cards.** A finished subagent tool call's card uses its run's recorded outcome when there is one, and the tool call's status otherwise. That keeps threads saved before this change, and subagents of external agents that use `_meta.subagent_session_info`, exactly as before. A running card still reads its tool call, so a new run never briefly shows the previous run's outcome. The subagent titlebar uses the reported state only once some has been received. Release Notes: - N/A |
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory/skills | ||
| .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.