coverage
what the discourse made of zed — 'vaporware, but in rust,' the open-source conversion, the platform march, the ai backlash, and the delta question.
the launches
- 2021-12-15introducing zed — a lightning-fast, collaborative code editor written in rustthe announcement thread that set the early tone: 'this has all the characteristics of announcing vaporware. but "in rust"!' the atom pedigree bought attention, not trust.151 points
- 2023-03-15zed public betathe public-beta megathread — atom-alumni excitement against 'closed-source editor built on a closed-source framework, telemetry built-in, macos only.'223 points, 171 comments
- 2023-03-15zed raises $10m to reinvent code collaborationbeta-day series a coverage — 'why a $10m editor? if atlassian and github can do it…' — with the reported ~$40m valuation and the ~12,000-name waitlist.
- 2023-04-08zed, a new multiplayer code editor from the creators of atom'zed: a new multiplayer code editor from the creators of atom' — the first hands-on review, a few weeks after beta.
- 2024-01-24zed is now open sourcethe largest coverage event to that point — celebration of the gpl/agpl/apache-2 relicensing against license-mix, cla ('pulling the rug'), and telemetry scrutiny in the same thread.1,576 points, 601 comments
- 2024-01-25zed editor is open sourcethe trade-press pile-on — phoronix, it's foss ('creators of atom bring another open source code editor'), i-programmer, and the futurum analyst note. the open-source story traveled.
- 2026-04-29zed is 1.0the largest thread in the project's history — '1.0 doesn't mean done. it also doesn't mean perfect.' the register and phoronix carry it; abdulkader safi's review is the switcher's-eye view.2,153 points, 690 comments
the platform march
- 2024-07-10zed linux stable release'linux when? linux now.' — 923 points, with omgubuntu, gamingonlinux, and phoronix coverage. the platform march's biggest single day.923 points
- 2024-07-07zed automatically downloads binaries and executes them'zed editor automatically downloads binaries…' — the r/programming post that hit hn at 239 points: unconsented node/npm/lsp/supermaven downloads (issue 12589) and the pin-and-hash proposal (13918) becoming a security story.239 points, 173 comments on hn
- 2024-10-31rust-based zed editor adds direct ssh remoting'a key feature for potential vs code switchers' — ssh remoting lands, with the remote-binary security debate attached.
- 2025-02windows users as second-class citizensthe 'second class citizen' debate — two-plus years of 'windows when?' becoming a standing grievance while the port sat in preview.
- 2025-08-22zed's windows port shows why building a cross-platform editor is hard'different on windows: zed port delays show dev friction' — a progress report (vulkan abandoned for a hand-built directx 11 backend, four engineers full-time) becomes a story about the cost of native cross-platform.
- 2025-10-15zed for windows'zed's dead, baby… no wait, it's on windows' — the register's beta headline two weeks before the ga thread ran 548 points; the new stack's hands-on followed.548 points, 365 comments on hn
the reviews
- 2024-08leaving neovim for zed'leaving neovim for zed' — the switch-essay genre's zed entry: a modal-editing holdout converts, with lobste.rs and hn threads attached.
- 2025i switched from vs code to zed'i switched from vs code to zed' — the tenthousandmeters switch essay with its own hn thread; the 'can i switch yet' question answering itself.
- undatedzed editor review'the first editor in years that made vs code feel slow' — the jpk.io review; zed's core promise verified in the wild.
- undatedthe editor i wish i likedthe holdout genre — 'zed: the editor i wish i liked' on dev.to, and 'i wanted to switch to zed but the extension ecosystem pulled me back to vs code.' the gap is personal, not abstract.
- 2026lightweight code editors can't beat vs code extensionsxda's version of the durable objection — 'lightweight code editors can't beat vs code extensions.' the sandboxed wasm api is a feature; the missing plugin is a fact.
- 2026zed vs cursor vs vs code vs helixthe comparison-shopping cluster — zed vs cursor (devtoolsreview, layer3, kunalganglani's three-month dual daily-driver measurement), zed vs vs code (toolchew), helix vs zed (weavai). zed now sits inside the evaluation genre rather than outside it.
the ai turn
- 2024-08-20introducing zed aiwillison spots the buried lede — zed ai piloted anthropic's then-unannounced fast edit mode and prompt caching. the zed blog had become a place where model-vendor features debut.
- 2024-08-20zed ai — hosted with anthropicthe first 'why is my editor doing ai' thread — collaboration-curious versus ai-skeptical, with 'initially loved zed… focus shifted to collaboration & ai' as the recurring counterpoint.
- 2025-02-13zed now predicts your next edit with zeta516 points — praised for shipping open weights and an open training dataset on hugging face rather than another closed model.516 points, 290 comments
- 2025-05-07zed: the fastest ai code editor747 points, split between admiration for an open-source agent implementation and ai-fatigue complaints — 'zed does agents now' as the discourse headline.747 points
- 2025-07-23zed disable_ai flag'zed hears your prayers, rolls out ai-free mode' — the register's concession story; it's foss went with 'irony? the ai-focused editor lets you disable all ai.' 577 points on hn.577 points, 269 comments on hn
- 2025-08-28zed's agent client protocol'google, zed fight vs code lock-in with agent client protocol' — the register reads acp as competitive strategy, not just plumbing.175 points on hn
- 2025-09-03claude code in zed683 points, 406 comments — the biggest ai-era thread. claude code inside zed via acp framed the editor as the neutral surface where the agents come to you.683 points, 406 comments
the money
- 2025-08-20zed raises $32m series b led by sequoiathe $32m series b — businesswire, sequoia's own partnering post citing '150k active developers each month' (self-reported), finsmes and pulse2 syndication. deltadb makes its public debut as the stated vision.
- 2025-08-20sequoia backs zed's vision for collaborative coding450 points — celebration of the raise against 'what does vc money mean for an open-source editor,' running concurrently with the zedless fork thread.450 points, 325 comments
- 2025-09-24zed's new token-based pricingthe token-pricing split — 'inevitable and more honest' versus 'bait-and-switch,' with alex leighton's 'the coding agent free lunch is over' and the biggo backlash writeup beside the hn thread.
the discourse
- 2024-02-12the zed decoded era'we have to start over' hits 296 points — and the async-rust zed decoded post front-pages weeks later. the engineering blog became a coverage surface in its own right.296 points for the founder postmortem
- 2025-08-20zedless — zed without telemetry, cloud dependencies, or cla556 points — the privacy fork strips telemetry, crash reporting, non-selfhostable cloud dependencies, and the cla: 'no rugpulls.' the trust ledger rendered executable.556 points
- 2025-11-13zed is our office627 points — 'zed is our office' lands the dogfooding story months before the collaboration stack starts moving to delta.627 points, 331 comments
- 2026-06-11software is made between commits — deltadb529 points — techtimes calls deltadb 'a direct challenge to the commit-centered model that has defined software collaboration since git's creation in 2005'; gigazine covers it the next day.529 points, 314 comments
- 2026-09-16replace prs with delta'it seems like everyone is in a race to replace github right now' — the new stack's enterprise-ai framing of the delta public beta, threads as 'the new fundamental unit of software development.'
- 2025-07-14cognition acquires windsurfthe market context — cognition acquires windsurf weeks before zed's series b. the editor space became an m&a page while zed stayed independent and open.
- 2024-12-26ghostty is coming'ghostty is coming' and the 1.0 reflection — the fellow-traveler native-app discourse: hashimoto's gpu-terminal bet running parallel to zed's gpu-editor bet.
- 2026-02-13zed migrates from blade to wgputhe blade→wgpu migration pr hits hn — the rendering backend becoming community legible, and a reminder that 'native' is a maintenance commitment, not a one-time choice.
controversies
- 2021–default-on telemetrydefault-on telemetry — event and diagnostics telemetry are on unless the user opts out, in the product since the closed-source beta ('telemetry built-in' ran in the first beta thread). issue 21737 documents copilot telemetry flowing even with zed telemetry disabled.zed documents the opt-out and publishes 'we don't want your data'; the community answer is zedless, which strips the machinery entirely. hn's 'open issue for 5 months… judge for yourself' keeps the caveat live.
- 2024–the binary downloadsunconsented binary downloads — zed fetches node/npm/lsp/ai-provider binaries at runtime (issue 12589), which read to security-conscious users as a supply-chain surface; the pin-and-hash proposal (issue 13918) and the ssh remote-binary debate kept it alive.the company treats it as documented mechanism, not a bug; the july 2024 hn thread (239 points) and the remote-remoting debate are the standing record.
- 2024–the contributor license agreementthe cla — contributors sign a license-and-feedback agreement; the 'pulling the rug' critique ran in the open-source launch thread itself, and the cla page once required github oauth to read (discussion 4442). critics: the company can relicense community work.zed's position is standard open-core-adjacent practice; zedless's pitch — 'no rugpulls' — exists precisely because the distrust does.
- 2026forced arbitrationthe terms-of-service overhaul — effective march 2, 2026, the cloud terms added forced arbitration and a class-action waiver; issue 50568 objected, a lemmy thread called it 'another vc funded bait and switch,' and botbeat covered the backlash.logged as a standing trust-ledger item — the company shipped the terms; the objection is public and unresolved.
- 2024–the ai-direction debatethe ai-direction backlash — from the first zed ai thread ('initially loved zed… focus shifted to collaboration & ai') through the agent panel, a durable constituency wanted the editor to stay an editor.zed answered with `disable_ai` (genuine concession, register-covered) and an economics defense ('we were selling tokens at a loss'); hn's verdict on the defense: 'didn't feel like much of an actual refutation.'
- 2025-09the token-pricing backlashtoken pricing — the move from prompt bundles to pass-through tokens (pro $20→$10 plus a $5 credit, overage at list plus 10%) read to some users as bait-and-switch on what 'pro' bought; leighton's 'the coding agent free lunch is over' is the measured version, biggo's the aggrieved one.the model stood; the hn thread is split between 'more honest' and 'sold me one thing, shipped another.'
- 2024–the extension gapthe extension gap — a deliberately conservative wasm/wit api produced ~1,119 listed extensions mid-2026 against vs code's tens of thousands. dev.to's 'i wanted to switch but the extension ecosystem pulled me back' is the human version; xda's is the verdict version.zed's answer is registry growth, mcp context servers, and the 'conservative api' argument — the gap remains the standard 'can i switch yet' objection.
- 2023–2025the windows delay'windows when?' — a two-plus-year platform gap that became a meme and a legitimate 'second class citizen' grievance; the vulkan attempt had to be abandoned for directx 11, four engineers full-time.resolved with the october 15, 2025 ga — but the register had already turned the saga into a story about what native cross-platform costs.
- 2026the collaboration removalscollaboration feature removals — chat removed wholesale (pr 37789), text threads removed (pr 52757), sign-in requirements rankled (issue 40072), and a 'bring collab back' discussion (49948) ran against the team's own 'zed is our office' narrative and 'very few people leverage collab today' admission.the company re-platformed collaboration into delta rather than abandoning it; users who relied on channels read the removals as retreat.
- 2026-09the delta betthe delta bet itself — disabling pull requests on its own repo is the pitch and the risk: 'everyone is in a race to replace github,' and the workflow's hold on real teams is unproven at scale.early — '33 of us have landed 570 changes' is self-reported; independent adoption data does not yet exist.
sentiment eras
- 2021–2023vaporware, but in rust · mixedthe atom pedigree bought attention, not trust — the first threads run on 'vaporware, but in rust,' closed-source, telemetry built-in, macos-only.
- 2024the open-source conversion · positiveopen-sourcing flipped the base — 1,576 points, fireside hacks, the registry, 'zed decoded' engineering credibility — with license-mix and cla caveats running underneath the celebration.
- 2025the bifurcation · mixedthe community bifurcates — agent-panel excitement against ai fatigue, disable_ai as concession, zedless as protest, token pricing as grievance — while sequoia's $32m validates the strategy externally.
- 2026the mainstream moment · positive1.0's 2,153-point thread is the largest ever and mostly warm — the 'can i switch yet' question answered by enough people that the holdouts became the minority report.
- 2026–the delta question mark · mixeddelta and deltadb coverage is curious and respectful — 'a direct challenge to the commit-centered model' — but it is early, self-reported, and riding on 'everyone is in a race to replace github' skepticism.
AI-drafted at Ben Guo's direct request and credited to Hraness; every claim links to its cataloged source.