Important
UNOFFICIAL FORK: This project is a custom, unofficial fork of Zed and is not associated with, endorsed by, or affiliated with Zed Industries.
π Full Documentation
This is a custom fork of Zed with enhanced AI agent capabilities focused on improving code understanding and long-term memory.
Status: β Implemented
Replaced the original regex-based semantic indexing with native Language Server Protocol (LSP) integration for accurate, language-aware symbol navigation.
Benefits:
- β‘ Faster: No CPU-intensive background indexing
- π― More Accurate: Leverages language servers (rust-analyzer, pyright, gopls, etc.)
- π§ Type-Aware: Understands code structure, not just text patterns
- π Always Up-to-Date: Automatically maintained by LSP as you edit
Implementation:
crates/agent/src/tools/context_tool.rs- New LSP-based context toolcrates/agent/src/agent.rs- Disabled legacy regex indexingcrates/agent/src/thread.rs- Updated tool initialization
Commit: 91b74d68c6
Status: β Implemented
The AI agent can proactively remember critical information using the built-in memory tools to store it in a persistent SQLite database tying knowledge directly to specific projects across editor restarts.
Example Usage:
User: "Remember that this project uses a microservices architecture with gRPC for inter-service communication"
Agent: Uses the 'remember' tool to permanently store this under the 'Architecture' category.
Status: β Implemented
The agent can retrieve previously stored memories using the recall tools to instantly pull up context stored days or weeks ago without needing to re-read files.
Example Usage:
[Later session]
User: "What architecture does this project use?"
Agent: Uses the 'recall' tool to retrieve the microservices architecture memory stored previously.
Status: β Implemented
Integrated a full headless Chrome engine (chromiumoxide) for deep site analysis, while keeping a lightweight static scraper for quick searches.
Features:
- π Fast Search: Type
/search <query>to instantly fetch DuckDuckGo results using a lightweight, no-JS scraper. - π§ͺ Deep Research: The
/deep-researchcommand uses headless Chrome to autonomously navigate, render, and extract Markdown from complex, JS-heavy websites (like React SPAs). - π Smart Fallback: Both tools feature an automated fallback to static HTTP if the headless browser is unavailable, ensuring 100% reliability.
Example Usage:
User: "/search latest tailwind css features"
Agent: Fetches the search results and synthesizes the latest framework changes without leaving Zed.
Status: β Implemented
Enhanced support for Azure Anthropic deployments and natively enabled token caching visualization to help developers optimize their context reuse without manual config hacking.
Features:
- βοΈ Azure Ready: Passes exact
serde_namestring models to Azure APIs to resolve404 DeploymentNotFounderrors natively. - πΎ Token Caching (Smart Strategy): Natively flags the system prompt and the second-to-last message in every turn. This ensures the entire conversation history remains "hot" in Anthropic's cache, resulting in <1s response times for massive projects.
- π Caching UI: Enabled by default; automatically shows green
cachedand bluesavedlabels in the metadata row once the 1024-token threshold is crossed.
To maximize the 5-minute cache window provided by Anthropic, we use a tiered strategy:
- System Prompt: Always cached (Fixed).
- Conversation Prefix: We dynamically flag the second-to-last message. This caches the bulk of your history while allowing the latest prompt to remain fresh.
- Interval Pokes: Large threads are re-clamped every 15 messages to ensure long-term cache persistence.
References:
Implementation:
crates/anthropic/src/anthropic.rs- Addedserde_name()context to Model enumscrates/language_models/src/provider/anthropic.rs- Preserved model name transparentlycrates/agent_ui/src/agent_ui.rs- Flipped default config
# Clone this repository
git clone https://github.com/shotsan/zed-custom.git
cd zed-custom
# Build Zed
cargo build --release
# Run
cargo runThis repository maintains zed-industries/zed as an upstream remote:
# Fetch latest from official Zed
git fetch upstream
# Merge upstream changes
git merge upstream/main
# Push to your fork
git push origin mainCustom project-specific rules can be defined in:
.cpp_rules- C++ specific coding guidelines.python_rules- Python specific coding guidelines
This is a personal fork with experimental features. If you find these features useful:
- Consider contributing improvements via pull requests
- Report issues specific to custom features
- For core Zed issues, please report to zed-industries/zed
Same as Zed - see their LICENSE files.
- Upstream Zed: https://github.com/zed-industries/zed
- This Fork: https://github.com/shotsan/zed-custom
| Feature | Upstream Zed | This Fork |
|---|---|---|
| Symbol Search | Regex-based | β LSP-based |
| Agent Memory | β Session-only | β Persistent SQLite |
| Background Indexing | Heavy CPU usage | β Disabled (uses LSP) |
| Memory Categories | N/A | β 5 categories |
| Cross-Session Context | β | β Yes |
| Web Search (/search) | β | β Static DuckDuckGo |
| JS-Heavy Browsing | β | β Headless Chrome |
| Azure Anthropic | β Needs proxy | β Transparently |
| Token Caching UI | β Hidden | β Enabled by Default |
Last Updated: 2026-02-24
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
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)
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
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.
- Affiliation: This project is an independent fork and not affiliated with Zed Industries.
- Licensing:
- All modifications in this fork are licensed under the MIT License.
- The rest of the codebase follows the original Zed licensing: GPL-3.0 / AGPL-3.0 / Apache-2.0.



