Discofork
Repository brief

zed-industries/zed

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T10:56:08.349Z
3mo ago

zed-industries/zed

Zed is an active, high-star Rust code editor repository with a very large fork base. It is a high-performance, multiplayer editor from the creators of Atom and Tree-sitter, with current development clearly ongoing on `main` and frequent recent commits. Forks are most likely interesting if you want to build on a large, actively maintained editor codebase with collaboration, AI, terminal, LSP, and platform-specific UI work already present.

GitHub
Loading tags...
Stars78,139
Forks7,600
Default branchmain
Last pushed2026-03-30T10:41:24Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

20 of 20 fork briefs
Selected

Choose this fork if you want a browser-integrated, workspace-centered Zed variant and are comfortable with significant divergence from upstream. Avoid it if you need close compatibility with upstream Zed, stable long-term mergeability, or the broadest set of untouched editor workflows.

Choose this fork if you need a heavily customized Zed base with remoting and editor changes and can afford ongoing fork maintenance. Choose upstream if you want current Zed features, active fixes, and lower merge risk.

Choose this fork only if you want an almost stock Zed checkout and plan to add your own changes later. If you want the latest editor fixes and polish, upstream is the better choice right now.

Choose this fork only if you want a deeply customized Zed variant and are willing to carry merge and maintenance burden. If you want current upstream features and fixes, stick with upstream Zed.

Choose this fork only if its custom workflow direction matches your goal and you are prepared to own long-term merge and maintenance work. If you want a current, broadly supported Zed base, upstream is the safer choice.

Choose this fork if you want a customized, fast-moving Zed variant and are comfortable owning divergence. Skip it if you want the lowest-risk path to current upstream Zed or need broad compatibility with upstream behavior and updates.

Choose this fork if you want a Windows-focused Zed derivative with extra remote/devcontainer/AI integration and can tolerate upstream drift. Avoid it if you need the lowest-maintenance path to upstream Zed or depend on upstream parity.

Choose this fork only if you want an almost-vanilla Zed base. If you want the latest upstream behavior or any added capabilities, upstream is the safer choice.

Prefer this fork only if ACP extensions and its downstream editor/agent changes are the goal. If you want the most stable, current Zed base, upstream is the better choice because this fork is heavily diverged and appears stale relative to active mainline.

Choose this fork if you want a highly customized, agentic Zed derivative and are willing to own ongoing merge and maintenance work. Choose upstream if you want the latest editor, collaboration, LSP, terminal, and platform fixes with lower operational risk.

Prefer this fork only if its Haskell-oriented changes are the point. For most users, upstream Zed is the safer choice because this fork is far behind and significantly diverged.

Choose this fork if you want a markedly customized Zed base centered on agent/conversation and workflow experimentation. Avoid it if you want to stay close to upstream, minimize merge risk, or rely on the latest editor fixes.

Choose this fork only if you want a customized Zed variant and are prepared to maintain a large divergence. For most adopters, upstream Zed is the safer choice because this fork is older, heavily modified, and likely missing recent fixes and features.

Choose this fork if you want a customized Zed with workflow-heavy UI changes and can tolerate major divergence from upstream. Avoid it if you want a low-maintenance base that stays close to current Zed releases.

Choose this fork if you want a customized Zed distribution with substantial assistant/workflow rework and you are willing to trade away upstream compatibility. Avoid it if you need the latest upstream Zed behavior, stable auth integrations, or low-maintenance syncing.

Choose this fork if you want a deeply customized Zed with agent/collab/workflow changes and you can absorb the cost of a large upstream gap. Choose upstream if you want the safer path for compatibility, fresh fixes, and lower maintenance burden.

Prefer this fork if you need web-platform support or want to build a specialized Zed variant. Avoid it if you want a low-maintenance downstream of upstream Zed, because the fork is heavily divergent and appears to lag many recent upstream changes.

Prefer this fork only if you need an old, Windows-focused Zed baseline to customize. If you want a maintained editor codebase or current upstream features, the fork is too stale and too far diverged.

Prefer this fork only if you want its custom May-2024-era editor/assistant experimentation and are willing to carry a large merge debt. For most adopters, upstream is the better base because this fork is stale and materially behind on ongoing Zed work.

Choose this fork only if you want an almost-vanilla Zed checkout. It does not currently add capabilities over upstream, and it is already behind on several recent fixes and polish commits, so it is a poor choice if you want a maintained or differentiated fork.