9be436b1ef5bfa19f759248ccab2a72b1256d704
<img width="707" height="778" alt="Screenshot 2026-01-07 at 8 34 00 PM" src="https://github.com/user-attachments/assets/59842820-079b-4d47-9bdd-f77300f8a60e" /> When the user presses Esc or the Stop button to interrupt a thread, terminal tools now capture their output and include it in the tool result. This allows the model to see what was happening in the terminal when the user interrupted, so it can answer questions about the output. ## Changes - `Thread::cancel()` now returns a `Task` that waits for tools to respond to cancellation before flushing pending messages - Terminal tool uses `select!` to detect cancellation signal and immediately kills the terminal and captures output - `run_turn_internal` uses `select!` to break out of event loop on cancel - Added test for terminal tool cancellation output capture This is a follow-up to #46218 which added similar functionality for the "Stop" button on individual terminal tool cards. Release Notes: - Interrupting the agent now captures terminal output so the model can see what was running when you stopped it
docs: Update "Custom Keybindings for Extension-Based Agents section" to include a troubleshooting note for defining an agent name (#46144)
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 issue)
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
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.
Languages
Rust
94.9%
JSON-with-Comments
2.7%
Python
0.8%
Inno Setup
0.3%
Tree-sitter Query
0.3%
Other
0.5%