Mikhail ButvinandClaude Opus 4.6
084eadfd0c
## Summary Paths inside parentheses without a preceding space (e.g. `Update(.claude/skills/sandbox/SKILL.md)` or `Write(/test/cool.rs)` from Claude Code output) were not clickable in the terminal. The `(` character was allowed as a middle character in the default path hyperlink regex, causing the entire `Update(.path/here` to be matched as a single invalid path. **Changes:** - Remove `(` from the middle-chars alternation (`[:(]` → `:`) in the default path hyperlink regex, so `(` always acts as a path boundary — consistent with it already being excluded from first and last character sets. Preserves upstream's space exclusion after `:`. - Iterate all regex matches in the line instead of only the first, so the correct path (which may be the second match after a prefix like `Update`) is found. This also simplifies the code by removing the separate hovered-word search logic. **Known tradeoff:** Filenames with parentheses in the middle (e.g. `docker-compose.prod(copy).yml`) are no longer matched as a single path. This is uncommon in terminal output contexts (compiler errors, stack traces, tool output) and is documented with a `should_panic` test. **What doesn't break:** - `(/path/file.js:321:13)` — `(` at word start is excluded by the first-char rule (unchanged) - Node.js stack traces like `at fn (/path/file.js:10:5)` — space before `(` makes it a separate word - All 38 terminal hyperlink tests pass Related: #18556, #23774 Release Notes: - Fixed terminal path detection for paths inside parentheses without preceding space (e.g. `Update(path)` or `Write(path)` patterns from CLI tool output) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
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.