Skip to content

shotsan/zed-custom

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

34,814 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Zed Custom - Enhanced AI Agent Features

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.

πŸš€ Custom Features

1. LSP-Based Symbol Search

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:

Commit: 91b74d68c6


2. Agent Memory System: remember

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.

Remember Tool Demo


3. Agent Memory System: recall

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.

Recall Tool Demo


4. Instant Web Search & Deep Research

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-research command 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.

Search Tool Demo


5. Azure Anthropic & Token Caching UI

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_name string models to Azure APIs to resolve 404 DeploymentNotFound errors 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 cached and blue saved labels in the metadata row once the 1024-token threshold is crossed.

Azure Anthropic Token Caching Demo

The "Smart Caching" Mechanism

To maximize the 5-minute cache window provided by Anthropic, we use a tiered strategy:

  1. System Prompt: Always cached (Fixed).
  2. 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.
  3. Interval Pokes: Large threads are re-clamped every 15 messages to ensure long-term cache persistence.

References:

Implementation:


πŸ”§ Setup & Usage

Building from Source

# Clone this repository
git clone https://github.com/shotsan/zed-custom.git
cd zed-custom

# Build Zed
cargo build --release

# Run
cargo run

Syncing with Upstream Zed

This 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 main

πŸ“ Configuration Files

Custom project-specific rules can be defined in:

  • .cpp_rules - C++ specific coding guidelines
  • .python_rules - Python specific coding guidelines

🀝 Contributing

This is a personal fork with experimental features. If you find these features useful:

  1. Consider contributing improvements via pull requests
  2. Report issues specific to custom features
  3. For core Zed issues, please report to zed-industries/zed

πŸ“œ License

Same as Zed - see their LICENSE files.


πŸ”— Links


πŸ“Š Feature Comparison

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

Zed

Zed CI

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:

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 specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

πŸ“„ License & Affiliation

  • Affiliation: This project is an independent fork and not affiliated with Zed Industries.
  • Licensing:

About

Enhanced AI agent fork of Zed: persistent memory, LSP symbol search, headless web browsing & Azure Anthropic caching.

Topics

Resources

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages