mirror of
https://github.com/zed-industries/zed.git
synced 2026-05-31 19:05:00 +07:00
Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
94bf3a5b1f
Integrate Jupyter's `complete_request`/`complete_reply` and `inspect_request`/`inspect_reply` protocols into Zed's editor completion system. When a REPL session is active, a composite completion provider wraps the existing LSP provider to fetch completions from both the language server and the Jupyter kernel in parallel. Selecting a kernel completion triggers an inspect request to populate documentation. Context sent to the kernel is informed by how mainstream kernels (IJulia, ipykernel/xeus-python, IRkernel) actually implement these handlers: - For completion, send the runnable chunk surrounding the cursor (the same unit `run` would execute) rather than the whole buffer. Kernels expect cell-sized input, and sending unrelated code can mislead jedi or be wasted on REPL-style completers (IJulia, IRkernel) that only look at the local syntactic context. Reusing `runnable_ranges` keeps this aligned with the user's mental model and lets future improvements to chunk detection (e.g. Tree-sitter top-level node selection) carry over automatically. - For inspect, send only the candidate symbol with the cursor at its end. Every surveyed kernel resolves documentation by extracting the token at the cursor (`get_token` in IJulia, `token_at_cursor` in ipykernel, `.guessTokenFromLine` in IRkernel, regex in xeus-cling), and ipykernel's `do_inspect` does a live-namespace lookup rather than jedi-based scope analysis, so surrounding context yields no benefit. IHaskell additionally ignores `cursor_pos` and uses the last whitespace-separated chunk, so injecting any code after the symbol would actively break inspection there. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .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 | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| typos.toml | ||
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.