Public dossier section · @ben
the idea
This is @ben's profile revision 1. The original date and editorial confidence below are attributed to its publisher, not independent verification.
Original credited author: Hraness
AI-drafted at Ben Guo's direct request and credited to Hraness; every claim links to its cataloged source.
Back to the full profile · Markdown version · Original document
Published text
zed: the idea
the fast-editor-as-collaboration-layer idea — the lineage from engelbart through atom, what zed proved, what stalled, and what delta is for.
lineage
- 1968 — engelbart's nls and xanadu: the mother of all demos and the mother of all unbuilt software — sobo explicitly cites engelbart's nls/augment vision and doug's lost collaboration paradigm in the first zed post, and 'xanadu was waiting for agents' puts delta in the docuverse lineage. (sources: first blog post, sobos ted nelson essay)
- 2011–2022 — atom and electron: the first attempt — hackability plus usability on a webview shell, which delivered electron to the world and the performance ceiling to its own authors. 'we created electron to create atom, but i can't imagine a worse application for electron than a code editor.' (sources: atom public beta, by nathansobo, mit open-sourcing incl, definitive atom→zed postmortem interview, github announces atom archive for dec 15, 2022)
- 2013– — tree-sitter: the parser that outlived its editor — brunsfeld's incremental glr engine went to github.com, neovim, helix, and emacs, and became zed's syntax layer and extension-grammar format. (sources: tree-sitter initial commit, brunsfeld galois talk, brunsfeld on tree-sitter in zed, wasm/wit extension architecture)
- 2017 — teletype and crdts: the collaboration primitive — teletype's custom string-wise crdt proved real-time multi-cursor editing in production; 'conversations should happen close to code' became zed's founding assumption. (sources: teletype beta, qcon sf unveiling, first blog post)
- 2017–2019 — xray and memo: the failed rehearsal — xray's rust core and client/server crdt architecture died at github, but its memo side-project ('an operation-based version control system that tracks changes at the level of individual keystrokes') is the direct ancestor of deltadb eight years later. (sources: xray: rust-core experimental editor, github has decided not to move forward, memo = crdt vcs at keystroke level, deltadb detail)
- 2016 → 2025 — lsp → acp: the protocol precedent — lsp unbundled language intelligence from monolithic ides; acp applies the same move to agents. zed's stated strategy is to be the neutral surface rather than the deepest bundled model. (sources: acp + gemini cli, acp coverage, agents as extensions)
- 2018–2021 — the rust-native stack: the native-stack conviction — raph levien's rust ui writing and xi-editor experience as the cited nudge; gpu-rendered immediate-mode rust (gpui) as the only way to 'pixels on the next refresh of your display — every time.' (sources: definitive atom→zed postmortem interview, gpui 120fps gpu-ui rationale, gpui ownership/data flow (sobo), introducing zed manifesto landing page)
what zed proved
- the native editor works: a native, gpu-rendered editor can be built and loved — 'hundreds of thousands of developers' daily at 1.0 (self-reported), ~90k github stars, a two-year-long 'windows when?' demand curve, and 2,153 hn points for the 1.0 post. the speed claim is the moat. (sources: zed 1, created 2021-02-20, 2,153 pts/690 comments, 548 pts/365 comments)
- the open-source flywheel: open source is the distribution and the hiring engine — 1,576 points at relicensing, the registry grew to ~1,500 extensions in two years, the debugger shipped as a community-led effort, and 'hired through github' converted contributors into employees. (sources: 1,576 pts/601 comments, ~1,119 registry / ~1,562 tracked extensions, dap debugger launch, hiring-from-contributors program)
- agents come to the neutral surface: the neutral-surface bet works — google initiated contact for acp, jetbrains adopted it, claude code and codex and opencode and cursor all run inside zed. when the model vendors fight, the editor can host them all. (sources: acp + gemini cli, jetbrains acp collaboration, claude code beta in zed, codex via acp, zed 1)
- the craft is credible: the team keeps its own credential — the people who built atom's collaboration stack wrote the crdt papers' production sequel, and the engineering blog ('zed decoded') became a respected rust publication independent of the product. (sources: official bios + roster (~40 people), async rust deep-dive w/ video, 211 pts/88 comments, sobo essay)
- the post-commit world exists: the second half of the plan exists in code — deltadb and delta shipped to public beta with pull requests disabled on the company's own repo: '33 of us have landed 570 changes to main' (self-reported). the memo idea from 2018 is a running product. (sources: deltadb detail, delta private beta, delta public beta)
what stayed unfinished
- collaboration in the editor: collaboration inside the editor didn't stick — 'very few people leverage collab today' (company admission), the chat panel was removed wholesale, and channels survive as the office the team itself runs, not the product users adopted. (sources: windows sign-in reprompt, chat feature removed, company runs all-hands inside zed channels, delta private beta)
- the extension gap: the extension gap persists — a deliberately conservative wasm api produced ~1,119 listed extensions mid-2026 against vs code's tens of thousands; 'my one plugin isn't there' remains the standard switching objection. (sources: ~1,119 registry / ~1,562 tracked extensions, wasm/wasmtime + tree-sitter hybrid extension design, wasm/wit extension architecture)
- free ai: free ai didn't survive contact with the bill — free beta → at-cost billing → prompt bundles → token pass-through in eighteen months, each step read by some users as a smaller version of the same bait-and-switch. (sources: usage-based billing for high-volume users, $10 pro, 182 pts/197 comments, irwin: token pass-through economics)
- gpui for everyone: gpui as a standalone framework stays aspirational — apache-2 and documented, but unpublished as a supported crate; the community (gpui-component, loungy, zedis, termy) builds on it anyway, which is evidence for and against the 'ui framework for everyone' claim. (sources: gpui framework site, gpui third-party app catalog (loungy, zedis, termy, etc, longbridges gpui component library, gpui ownership/data flow (sobo))
- the ai trust ledger: the ai-direction argument never fully closed — disable_ai shipped as a genuine concession, yet zedless exists and 'not much of an actual refutation' was the hn verdict on the economics defense. (sources: disable_ai setting, privacy/local-first fork, skeptical hn reception, ai-free mode wry coverage)
the agent-era turn
- (for) the whole history points one direction — teletype's crdt collaboration, xray's operation-based memo, channels, acp, and deltadb are one fifteen-year project. the company isn't pivoting toward the agent era; the agent era finally caught up to what they were building. (sources: teletype beta, memo = crdt vcs at keystroke level, deltadb detail, sobos ted nelson essay)
- (against) the collaboration record cuts the other way — the team that argued 'conversations should happen close to code' watched 'very few people leverage collab today,' removed chat, and moved the bet to a separate app. delta is a relaunch, not a continuation. (sources: windows sign-in reprompt, chat feature removed, delta private beta, 627 pts/331 comments)
- (for) the neutral-surface strategy is correctly calibrated for a model-vendor knife fight — acp means zed doesn't have to out-model openai or anthropic, just out-host everyone. jetbrains adopting the protocol is the strongest external validation yet. (sources: acp + gemini cli, jetbrains acp collaboration, zed 1, acp coverage)
- (against) the economics are still unproven — the editor is free, ai tokens were sold at a loss until token billing, business seats are six months old, and delta's paid plans don't exist yet. sequoia's $32m is a bet on the second half of the plan, not a verdict on it. (sources: irwin: token pass-through economics, 1,100 contributors, zed for business launch, delta public beta)
- (nuance) the moat may be the stack rather than the editor — if deltadb wins, delta matters more than zed; if it doesn't, zed is an excellent editor in a market where the giants give editors away. the company's own framing already separates the two bets. (sources: deltadb detail, delta private beta, crdt explanation, 150k active developers each month (self-reported))
- (against) the trust ledger is the real ceiling — telemetry, cla, arbitration, token pricing, and feature removals each passed, but they compound into the question every 'can i switch yet' thread asks. zedless is the ledger made executable. (sources: privacy/local-first fork, contributor license and feedback agreement text, chat feature removed, 182 pts/197 comments)
- (for) the strongest evidence for delta is that the company runs on it — 'zed is our office' made the dogfooding literal, and disabling pull requests on delta's own repo is a risk no marketing team would fake. (sources: company runs all-hands inside zed channels, delta public beta, third-party delta coverage)
successors
- delta: the idea's own successor — the collaboration thesis grown into a separate product where threads replace pull requests. if it works, zed becomes the on-ramp, not the destination. (sources: delta private beta, delta public beta, delta product site)
- cursor: the opposite bet running at full speed — fork vs code, bundle the model, own the agent. the reference incumbent zed's neutral-surface strategy is defined against; cursor now also speaks acp. (sources: zed 1, 683 pts/406 comments)
- vs code + github: the incumbent stack zed has to displace twice — the editor monopoly atom's own electron enabled, plus the commit/pr workflow delta is built to replace. atom alumni now staff both sides. (sources: mit open-sourcing incl, sunset coverage, definitive atom→zed postmortem interview)
- warp: the road not taken — sobo's three-month employer built the agent workbench inside the terminal instead of the editor. same 'rebuild the tool for agents' impulse, different surface. (sources: sobos full founding narrative (xray→2019→warp→mar 2022 dogfood))
- zedless: the community fork as successor-with-an-asterisk — the editor thesis stripped of the company's services layer: no telemetry, no cla, no rugpulls. what gpl was always for. (sources: privacy/local-first fork, 556 pts/322 comments)
- jetbrains + acp: the protocol succeeding without zed — if acp becomes lsp-for-agents across the industry, the neutral-surface win outgrows the editor that minted it. (sources: jetbrains acp collaboration, acp + gemini cli)
open questions
- the series b valuation is undisclosed — sequoia led $32m at an unknown price; crunchbase news reports 'over $42m' total but no post-money figure.
- adoption is self-reported — '150k monthly active developers' comes from sequoia's blog, 'hundreds of thousands daily' from the 1.0 post; no independent measurement exists.
- does delta's 'threads replace prs' survive contact with real teams — 33 employees landing 570 changes on their own repo is evidence of dogfooding, not of the market?
- is the revenue model pro + business + delta plans enough to clear a $42m+ raise — or does the open editor stay subsidized by services that haven't yet proven their take rate?
- the warp ip separation is undocumented — how did the codebase sobo carried into warp for three months come back out clean?
- collab adoption inside zed stayed low — does the delta re-platforming fix a product problem or a demand problem that will follow it?
- does acp commoditize zed — if every editor speaks the protocol and the agents belong to the model vendors, what is the editor's durable position?
- the extension gap is structural — a sandboxed wasm api may never host the plugin surface vs code users expect; is 'conservative api' a strategy or a ceiling?
AI-drafted at Ben Guo's direct request and credited to Hraness; every claim links to its cataloged source.
Canonical page: https://hraness.com/zed/the-idea
Original source occurrences
- github announces atom archive for dec 15, 2022 · wayback machine · 2022-06-08 (day) · original ID: src-ci-atom-sunset · Other public citations of this URL
github announces atom archive for dec 15, 2022
- gpui third-party app catalog (loungy, zedis, termy, etc · github · undated (unknown) · original ID: src-ci-awesome-gpui · Other public citations of this URL
gpui third-party app catalog (loungy, zedis, termy, etc.)
- 1,100 contributors · businesswire.com · 2025-08-20 (day) · original ID: src-ci-businesswire-32m · Other public citations of this URL
1,100 contributors; 150k devs; "not forked vs code" framing
- contributor license and feedback agreement text · zed.dev · undated (unknown) · original ID: src-ci-cla · Other public citations of this URL
contributor license and feedback agreement text
- dap debugger launch · zed.dev · 2025-06-19 (day) · original ID: src-ci-debugger · Other public citations of this URL
dap debugger launch; hn 502 pts
- disable_ai setting · zed.dev · 2025-07-23 (day) · original ID: src-ci-disable-ai · Other public citations of this URL
disable_ai setting; onboarding toggle
- chat feature removed · github · 2025 (year) · original ID: src-ci-gh-remove-chat · Other public citations of this URL
chat feature removed; "sorry to the 5 of you"
- windows sign-in reprompt · github · 2025 (year) · original ID: src-ci-gh-signin-issue · Other public citations of this URL
windows sign-in reprompt; "very few people leverage collab today"
- longbridges gpui component library · github · undated (unknown) · original ID: src-ci-gpui-component · Other public citations of this URL
longbridge's gpui component library
- 211 pts/88 comments · hacker news · 2024-04-09 (day) · original ID: src-ci-hn-async-rust · Other public citations of this URL
211 pts/88 comments
- 683 pts/406 comments · hacker news · 2025-09-03 (day) · original ID: src-ci-hn-claude-code · Other public citations of this URL
683 pts/406 comments
- skeptical hn reception · hacker news · 2026-05 (month) · original ID: src-ci-hn-not-for-money · Other public citations of this URL
skeptical hn reception
- 182 pts/197 comments · hacker news · 2025-09-24 (day) · original ID: src-ci-hn-pricing · Other public citations of this URL
182 pts/197 comments; morgankrey replies
- 548 pts/365 comments · hacker news · 2025-10-15 (day) · original ID: src-ci-hn-windows · Other public citations of this URL
548 pts/365 comments
- 2,153 pts/690 comments · hacker news · 2026-04-29 (day) · original ID: src-ci-hn-zed-1-0 · Other public citations of this URL
2,153 pts/690 comments; tos/blob debates
- 627 pts/331 comments · hacker news · 2025-11-13 (day) · original ID: src-ci-hn-zed-office · Other public citations of this URL
627 pts/331 comments
- 1,576 pts/601 comments · hacker news · 2024-01-24 (day) · original ID: src-ci-hn-zed-open-source · Other public citations of this URL
1,576 pts/601 comments; license discussion; "calming editor" praise
- 556 pts/322 comments · hacker news · 2025-08-20 (day) · original ID: src-ci-hn-zedless · Other public citations of this URL
556 pts/322 comments
- wasm/wasmtime + tree-sitter hybrid extension design · zed.dev · 2024-04-18 (day) · original ID: src-ci-language-extensions · Other public citations of this URL · max brunsfeld
wasm/wasmtime + tree-sitter hybrid extension design
- $10 pro · zed.dev · 2025-09-24 (day) · original ID: src-ci-pricing-token · Other public citations of this URL
$10 pro; +10% pass-through; $5 credits
- ai-free mode wry coverage · theregister.com · 2025-07-30 (day) · original ID: src-ci-register-disable-ai · Other public citations of this URL
"ai-free mode" wry coverage
- crdt explanation · tech times · 2026-06-13 (day) · original ID: src-ci-techtimes-deltadb · Other public citations of this URL
crdt explanation; git-2005 framing; thursday waitlist
- gpui 120fps gpu-ui rationale · zed.dev · 2023 (year) · original ID: src-ci-videogame-gpui · Other public citations of this URL · antonio scandurra
gpui 120fps gpu-ui rationale; per-primitive shaders
- xray: rust-core experimental editor · github · 2018 (year) · original ID: src-ci-xray · Other public citations of this URL
xray: rust-core experimental editor; memo operation-based vcs
- async rust deep-dive w/ video · zed.dev · 2024-04-09 (day) · original ID: src-ci-zed-decoded-async · Other public citations of this URL · thorsten ball
async rust deep-dive w/ video
- company runs all-hands inside zed channels · zed.dev · 2025-11-13 (day) · original ID: src-ci-zed-office · Other public citations of this URL
company runs all-hands inside zed channels
- privacy/local-first fork · github · 2025-08-20 (day) · original ID: src-ci-zedless · Other public citations of this URL
privacy/local-first fork; no telemetry/cla/cloud deps
- atom public beta, by nathansobo · atom-editor.cc · 2014-02-26 (day) · original ID: src-hp-atom-intro · Other public citations of this URL · nathan sobo
atom public beta, by nathansobo
- mit open-sourcing incl · wayback machine · 2014-05-06 (day) · original ID: src-hp-atom-oss · Other public citations of this URL
mit open-sourcing incl. atom shell
- delta product site · delta.dev · 2026-09 (month) · original ID: src-hp-delta-dev · Other public citations of this URL
delta product site
- brunsfeld galois talk · galois.com · 2017-12-11 (day) · original ID: src-hp-galois-treesitter · Other public citations of this URL · max brunsfeld
brunsfeld galois talk; github.com+atom integration in progress
- created 2021-02-20 · github · 2026-09-16 (day) · original ID: src-hp-gh-zed-repo · Other public citations of this URL
created 2021-02-20; ~90.3k stars, ~10.6k forks; gpl-3.0
- ~1,119 registry / ~1,562 tracked extensions · github · 2026-06-22 (day) · original ID: src-hp-ghext-tracker · Other public citations of this URL
~1,119 registry / ~1,562 tracked extensions; type breakdown
- gpui framework site · gpui.rs · 2026-09 (month) · original ID: src-hp-gpui-rs · Other public citations of this URL
gpui framework site
- qcon sf unveiling · infoq.com · 2017-11 (month) · original ID: src-hp-infoq-teletype · Other public citations of this URL
qcon sf unveiling; webrtc + crdt details
- acp coverage · theregister.com · 2025-08-28 (day) · original ID: src-hp-register-acp · Other public citations of this URL
acp coverage; json-rpc over stdio
- 150k active developers each month (self-reported) · sequoiacap.com · 2025-08-20 (day) · original ID: src-hp-sequoia-partnering · Other public citations of this URL
"150k active developers each month" (self-reported); sequoia rationale
- sunset coverage · techcrunch · 2022-06-08 (day) · original ID: src-hp-tc-atom-sunset · Other public citations of this URL
sunset coverage; notes brunsfeld's new-editor effort
- teletype beta · github.blog · 2017-11-15 (day) · original ID: src-hp-teletype · Other public citations of this URL · antonio scandurra
teletype beta; author scandurra
- third-party delta coverage · thenewstack.io · 2026-09-16 (day) · original ID: src-hp-tns-delta · Other public citations of this URL
third-party delta coverage; recap of funding
- tree-sitter initial commit · github · 2013-11-06 (day) · original ID: src-hp-ts-commit · Other public citations of this URL
tree-sitter initial commit
- github has decided not to move forward · github · 2018 (year) · original ID: src-hp-xray-readme · Other public citations of this URL
"github has decided not to move forward"; memo subproject; update log
- memo = crdt vcs at keystroke level · github · 2018-05-28 (day) · original ID: src-hp-xray-update · Other public citations of this URL
memo = crdt vcs at keystroke level
- zed 1 · zed.dev · 2026-04-29 (day) · original ID: src-hp-zed-10 · Other public citations of this URL · nathan sobo
zed 1.0; >1m loc; daily-user claim; acp agent list incl. cursor
- acp + gemini cli · zed.dev · 2025-08-27 (day) · original ID: src-hp-zed-acp · Other public citations of this URL
acp + gemini cli; google approached zed
- agents as extensions · zed.dev · 2025-11-06 (day) · original ID: src-hp-zed-agent-ext · Other public citations of this URL
agents as extensions
- usage-based billing for high-volume users · zed.dev · 2024-10-17 (day) · original ID: src-hp-zed-ai-billing · Other public citations of this URL
usage-based billing for high-volume users
- irwin: token pass-through economics · zed.dev · 2026-05-05 (day) · original ID: src-hp-zed-ai-money · Other public citations of this URL · conrad irwin
irwin: token pass-through economics; long-term = deltadb monetization
- zed for business launch · zed.dev · 2026-05-06 (day) · original ID: src-hp-zed-business · Other public citations of this URL
zed for business launch
- claude code beta in zed · zed.dev · 2025-09-03 (day) · original ID: src-hp-zed-claude-code · Other public citations of this URL
claude code beta in zed
- codex via acp · zed.dev · 2025-10-16 (day) · original ID: src-hp-zed-codex · Other public citations of this URL
codex via acp
- sobo essay · zed.dev · 2025-06-12 (day) · original ID: src-hp-zed-craftsmanship · Other public citations of this URL
sobo essay
- first blog post · zed.dev · 2022-12-01 (day) · original ID: src-hp-zed-crdts · Other public citations of this URL · nathan sobo
first blog post; "16 years ago… 135k lines of rust"; engelbart framing
- delta private beta · zed.dev · 2026-08-12 (day) · original ID: src-hp-zed-delta · Other public citations of this URL · nathan sobo
delta private beta
- delta public beta · zed.dev · 2026-09-16 (day) · original ID: src-hp-zed-delta-public · Other public citations of this URL · nathan sobo
delta public beta; prs off on own repo; "race to replace github"; 33 people/570 changes; free-during-beta
- deltadb detail · zed.dev · 2026-06-11 (day) · original ID: src-hp-zed-deltadb · Other public citations of this URL · nathan sobo
deltadb detail; "founded zed to move beyond the constraints of commits"; first spoke fall 2025
- wasm/wit extension architecture · zed.dev · 2024-10-21 (day) · original ID: src-hp-zed-extensions-decoded · Other public citations of this URL
wasm/wit extension architecture; registry repo flow
- gpui ownership/data flow (sobo) · zed.dev · 2024-01-25 (day) · original ID: src-hp-zed-gpui-ownership · Other public citations of this URL
gpui ownership/data flow (sobo)
- hiring-from-contributors program · zed.dev · 2025-09-16 (day) · original ID: src-hp-zed-hired-gh1 · Other public citations of this URL
hiring-from-contributors program
- introducing zed manifesto landing page · wayback machine · 2022-06-08 (day) · original ID: src-hp-zed-introducing-2022 · Other public citations of this URL · nathan sobo
"introducing zed" manifesto landing page; waitlist era
- jetbrains acp collaboration · zed.dev · 2025-10-06 (day) · original ID: src-hp-zed-jetbrains-acp · Other public citations of this URL
jetbrains acp collaboration
- definitive atom→zed postmortem interview · zed.dev · 2024-02-12 (day) · original ID: src-hp-zed-start-over · Other public citations of this URL · thorsten ball
definitive atom→zed postmortem interview; sobo's 2017 moment; pathfinder/sdf detours
- brunsfeld on tree-sitter in zed · zed.dev · 2023-03-27 (day) · original ID: src-hp-zed-syntax-aware · Other public citations of this URL · max brunsfeld
brunsfeld on tree-sitter in zed
- official bios + roster (~40 people) · zed.dev · 2026-09-16 (day) · original ID: src-hp-zed-team · Other public citations of this URL
official bios + roster (~40 people)
- sobos full founding narrative (xray→2019→warp→mar 2022 dogfood) · zed.dev · 2023-01-23 (day) · original ID: src-hp-zed-week1 · Other public citations of this URL · nathan sobo
sobo's full founding narrative (xray→2019→warp→mar 2022 dogfood)
- sobos ted nelson essay · zed.dev · 2026-09-01 (day) · original ID: src-hp-zed-xanadu · Other public citations of this URL · nathan sobo
sobo's ted nelson essay
Structured research records
the whole history points one direction — teletype's crdt collaboration, xray's operation-based memo, channels, acp, and deltadb are one fifteen-year project. the company isn't pivoting toward the agent era; the agent era finally caught up to what they were building. · zed-agent-era-arguments
Original location · source-7011e74d4b91d41daa66 · source-13e118307cfd7499efe4 · source-b1eaf0c240eb91f6ad9b · source-1b7afa2697887b681bdb
Original structured fields
{ "claim": "the whole history points one direction — teletype's crdt collaboration, xray's operation-based memo, channels, acp, and deltadb are one fifteen-year project. the company isn't pivoting toward the agent era; the agent era finally caught up to what they were building.", "id": "arg-one-project", "side": "for", "sourceIds": [ "src-hp-teletype", "src-hp-xray-update", "src-hp-zed-deltadb", "src-hp-zed-xanadu" ] }the collaboration record cuts the other way — the team that argued 'conversations should happen close to code' watched 'very few people leverage collab today,' removed chat, and moved the bet to a separate app. delta is a relaunch, not a continuation. · zed-agent-era-arguments
Original location · source-4c037bbb714d9da82eec · source-ce36cc5f3be335ef5e12 · source-da3ae6d4dd42306c9587 · source-c0d12e8613ea7ce8392c
Original structured fields
{ "claim": "the collaboration record cuts the other way — the team that argued 'conversations should happen close to code' watched 'very few people leverage collab today,' removed chat, and moved the bet to a separate app. delta is a relaunch, not a continuation.", "id": "arg-collab-record", "side": "against", "sourceIds": [ "src-ci-gh-signin-issue", "src-ci-gh-remove-chat", "src-hp-zed-delta", "src-ci-hn-zed-office" ] }the neutral-surface strategy is correctly calibrated for a model-vendor knife fight — acp means zed doesn't have to out-model openai or anthropic, just out-host everyone. jetbrains adopting the protocol is the strongest external validation yet. · zed-agent-era-arguments
Original location · source-3313f1a2152843b33046 · source-962c08be4137872f243e · source-9d6d1b0fcfbb163b1d54 · source-b8da52dc3a8acdf6dac6
Original structured fields
{ "claim": "the neutral-surface strategy is correctly calibrated for a model-vendor knife fight — acp means zed doesn't have to out-model openai or anthropic, just out-host everyone. jetbrains adopting the protocol is the strongest external validation yet.", "id": "arg-neutral-surface", "side": "for", "sourceIds": [ "src-hp-zed-acp", "src-hp-zed-jetbrains-acp", "src-hp-zed-10", "src-hp-register-acp" ] }the economics are still unproven — the editor is free, ai tokens were sold at a loss until token billing, business seats are six months old, and delta's paid plans don't exist yet. sequoia's $32m is a bet on the second half of the plan, not a verdict on it. · zed-agent-era-arguments
Original location · source-ecab0ff6bb1f245b1827 · source-15b1b3a956c987d8ebef · source-08fac470f64f358503de · source-2687d4ddaa3bf8588b52
Original structured fields
{ "claim": "the economics are still unproven — the editor is free, ai tokens were sold at a loss until token billing, business seats are six months old, and delta's paid plans don't exist yet. sequoia's $32m is a bet on the second half of the plan, not a verdict on it.", "id": "arg-economics", "side": "against", "sourceIds": [ "src-hp-zed-ai-money", "src-ci-businesswire-32m", "src-hp-zed-business", "src-hp-zed-delta-public" ] }the moat may be the stack rather than the editor — if deltadb wins, delta matters more than zed; if it doesn't, zed is an excellent editor in a market where the giants give editors away. the company's own framing already separates the two bets. · zed-agent-era-arguments
Original location · source-b1eaf0c240eb91f6ad9b · source-da3ae6d4dd42306c9587 · source-043735cbd38ae4b0bce7 · source-f1ec87829e685cbc5d78
Original structured fields
{ "claim": "the moat may be the stack rather than the editor — if deltadb wins, delta matters more than zed; if it doesn't, zed is an excellent editor in a market where the giants give editors away. the company's own framing already separates the two bets.", "id": "arg-stack-moat", "side": "nuance", "sourceIds": [ "src-hp-zed-deltadb", "src-hp-zed-delta", "src-ci-techtimes-deltadb", "src-hp-sequoia-partnering" ] }the trust ledger is the real ceiling — telemetry, cla, arbitration, token pricing, and feature removals each passed, but they compound into the question every 'can i switch yet' thread asks. zedless is the ledger made executable. · zed-agent-era-arguments
Original location · source-31a0cb59bbce0e5a47a4 · source-7222d18917e95bf91cc3 · source-ce36cc5f3be335ef5e12 · source-0fa4d1d1b2e607963fb4
Original structured fields
{ "claim": "the trust ledger is the real ceiling — telemetry, cla, arbitration, token pricing, and feature removals each passed, but they compound into the question every 'can i switch yet' thread asks. zedless is the ledger made executable.", "id": "arg-trust-ceiling", "side": "against", "sourceIds": [ "src-ci-zedless", "src-ci-cla", "src-ci-gh-remove-chat", "src-ci-hn-pricing" ] }the strongest evidence for delta is that the company runs on it — 'zed is our office' made the dogfooding literal, and disabling pull requests on delta's own repo is a risk no marketing team would fake. · zed-agent-era-arguments
Original location · source-0e416df65a78b648674c · source-2687d4ddaa3bf8588b52 · source-da6e60eaf083e8adb637
Original structured fields
{ "claim": "the strongest evidence for delta is that the company runs on it — 'zed is our office' made the dogfooding literal, and disabling pull requests on delta's own repo is a risk no marketing team would fake.", "id": "arg-dogfood", "side": "for", "sourceIds": [ "src-ci-zed-office", "src-hp-zed-delta-public", "src-hp-tns-delta" ] }engelbart's nls and xanadu · zed-idea-lineage
Original location · source-ff16741c07bff2c694cd · source-1b7afa2697887b681bdb
Original structured fields
{ "contribution": "the mother of all demos and the mother of all unbuilt software — sobo explicitly cites engelbart's nls/augment vision and doug's lost collaboration paradigm in the first zed post, and 'xanadu was waiting for agents' puts delta in the docuverse lineage.", "era": "1968", "id": "lin-engelbart", "name": "engelbart's nls and xanadu", "sourceIds": [ "src-hp-zed-crdts", "src-hp-zed-xanadu" ] }atom and electron · zed-idea-lineage
Original location · source-160fb2dc72205bfb9068 · source-5c85b6e328da996c46d8 · source-e2b799eee212ef0094c5 · source-d3f6cde8c2ae3bbb5925
Original structured fields
{ "contribution": "the first attempt — hackability plus usability on a webview shell, which delivered electron to the world and the performance ceiling to its own authors. 'we created electron to create atom, but i can't imagine a worse application for electron than a code editor.'", "era": "2011–2022", "id": "lin-atom", "name": "atom and electron", "sourceIds": [ "src-hp-atom-intro", "src-hp-atom-oss", "src-hp-zed-start-over", "src-ci-atom-sunset" ] }tree-sitter · zed-idea-lineage
Original location · source-104e9376beb811c47118 · source-c14a86ec479a178d0e75 · source-7c5529c0bd7c8f2615f4 · source-9c44f75dd5b99896093a
Original structured fields
{ "contribution": "the parser that outlived its editor — brunsfeld's incremental glr engine went to github.com, neovim, helix, and emacs, and became zed's syntax layer and extension-grammar format.", "era": "2013–", "id": "lin-tree-sitter", "name": "tree-sitter", "sourceIds": [ "src-hp-ts-commit", "src-hp-galois-treesitter", "src-hp-zed-syntax-aware", "src-hp-zed-extensions-decoded" ] }teletype and crdts · zed-idea-lineage
Original location · source-7011e74d4b91d41daa66 · source-2142f64f33561451a5a9 · source-ff16741c07bff2c694cd
Original structured fields
{ "contribution": "the collaboration primitive — teletype's custom string-wise crdt proved real-time multi-cursor editing in production; 'conversations should happen close to code' became zed's founding assumption.", "era": "2017", "id": "lin-teletype", "name": "teletype and crdts", "sourceIds": [ "src-hp-teletype", "src-hp-infoq-teletype", "src-hp-zed-crdts" ] }xray and memo · zed-idea-lineage
Original location · source-ac125f6bdd14737b9b41 · source-c27d180cd721c576b36e · source-13e118307cfd7499efe4 · source-b1eaf0c240eb91f6ad9b
Original structured fields
{ "contribution": "the failed rehearsal — xray's rust core and client/server crdt architecture died at github, but its memo side-project ('an operation-based version control system that tracks changes at the level of individual keystrokes') is the direct ancestor of deltadb eight years later.", "era": "2017–2019", "id": "lin-xray-memo", "name": "xray and memo", "sourceIds": [ "src-ci-xray", "src-hp-xray-readme", "src-hp-xray-update", "src-hp-zed-deltadb" ] }lsp → acp · zed-idea-lineage
Original location · source-3313f1a2152843b33046 · source-b8da52dc3a8acdf6dac6 · source-e3659ec3d16b9931343b
Original structured fields
{ "contribution": "the protocol precedent — lsp unbundled language intelligence from monolithic ides; acp applies the same move to agents. zed's stated strategy is to be the neutral surface rather than the deepest bundled model.", "era": "2016 → 2025", "id": "lin-lsp-acp", "name": "lsp → acp", "sourceIds": [ "src-hp-zed-acp", "src-hp-register-acp", "src-hp-zed-agent-ext" ] }the rust-native stack · zed-idea-lineage
Original location · source-e2b799eee212ef0094c5 · source-c2133aa117334d4b93e6 · source-cbe83a45ab27cd714954 · source-6854ebb7032c88d66bcb
Original structured fields
{ "contribution": "the native-stack conviction — raph levien's rust ui writing and xi-editor experience as the cited nudge; gpu-rendered immediate-mode rust (gpui) as the only way to 'pixels on the next refresh of your display — every time.'", "era": "2018–2021", "id": "lin-native-stack", "name": "the rust-native stack", "sourceIds": [ "src-hp-zed-start-over", "src-ci-videogame-gpui", "src-hp-zed-gpui-ownership", "src-hp-zed-introducing-2022" ] }the series b valuation is undisclosed — sequoia led $32m at an unknown price; crunchbase news reports 'over $42m' total but no post-money figure. · zed-idea-open-questions
Original structured fields
{ "text": "the series b valuation is undisclosed — sequoia led $32m at an unknown price; crunchbase news reports 'over $42m' total but no post-money figure." }adoption is self-reported — '150k monthly active developers' comes from sequoia's blog, 'hundreds of thousands daily' from the 1.0 post; no independent measurement exists. · zed-idea-open-questions
Original structured fields
{ "text": "adoption is self-reported — '150k monthly active developers' comes from sequoia's blog, 'hundreds of thousands daily' from the 1.0 post; no independent measurement exists." }does delta's 'threads replace prs' survive contact with real teams — 33 employees landing 570 changes on their own repo is evidence of dogfooding, not of the market? · zed-idea-open-questions
Original structured fields
{ "text": "does delta's 'threads replace prs' survive contact with real teams — 33 employees landing 570 changes on their own repo is evidence of dogfooding, not of the market?" }is the revenue model pro + business + delta plans enough to clear a $42m+ raise — or does the open editor stay subsidized by services that haven't yet proven their take rate? · zed-idea-open-questions
Original structured fields
{ "text": "is the revenue model pro + business + delta plans enough to clear a $42m+ raise — or does the open editor stay subsidized by services that haven't yet proven their take rate?" }the warp ip separation is undocumented — how did the codebase sobo carried into warp for three months come back out clean? · zed-idea-open-questions
Original structured fields
{ "text": "the warp ip separation is undocumented — how did the codebase sobo carried into warp for three months come back out clean?" }collab adoption inside zed stayed low — does the delta re-platforming fix a product problem or a demand problem that will follow it? · zed-idea-open-questions
Original structured fields
{ "text": "collab adoption inside zed stayed low — does the delta re-platforming fix a product problem or a demand problem that will follow it?" }does acp commoditize zed — if every editor speaks the protocol and the agents belong to the model vendors, what is the editor's durable position? · zed-idea-open-questions
Original structured fields
{ "text": "does acp commoditize zed — if every editor speaks the protocol and the agents belong to the model vendors, what is the editor's durable position?" }the extension gap is structural — a sandboxed wasm api may never host the plugin surface vs code users expect; is 'conservative api' a strategy or a ceiling? · zed-idea-open-questions
Original structured fields
{ "text": "the extension gap is structural — a sandboxed wasm api may never host the plugin surface vs code users expect; is 'conservative api' a strategy or a ceiling?" }the native editor works · zed-idea-proved
Original location · source-9d6d1b0fcfbb163b1d54 · source-69d3f4b8695b54fcce03 · source-101e8156590ce612a922 · source-327091314ee6dba9b640
Original structured fields
{ "detail": "a native, gpu-rendered editor can be built and loved — 'hundreds of thousands of developers' daily at 1.0 (self-reported), ~90k github stars, a two-year-long 'windows when?' demand curve, and 2,153 hn points for the 1.0 post. the speed claim is the moat.", "id": "clm-proved-native", "sourceIds": [ "src-hp-zed-10", "src-hp-gh-zed-repo", "src-ci-hn-zed-1-0", "src-ci-hn-windows" ], "title": "the native editor works" }the open-source flywheel · zed-idea-proved
Original location · source-3b51ee7a1bd8b106ff27 · source-335be0c9128cb6cfa326 · source-e49db740480048c513f8 · source-b5201c7ef317d9e4c82f
Original structured fields
{ "detail": "open source is the distribution and the hiring engine — 1,576 points at relicensing, the registry grew to ~1,500 extensions in two years, the debugger shipped as a community-led effort, and 'hired through github' converted contributors into employees.", "id": "clm-proved-oss-flywheel", "sourceIds": [ "src-ci-hn-zed-open-source", "src-hp-ghext-tracker", "src-ci-debugger", "src-hp-zed-hired-gh1" ], "title": "the open-source flywheel" }agents come to the neutral surface · zed-idea-proved
Original location · source-3313f1a2152843b33046 · source-962c08be4137872f243e · source-d814054e5499f85b7b83 · source-d3697d72719eab0fd0a3 · source-9d6d1b0fcfbb163b1d54
Original structured fields
{ "detail": "the neutral-surface bet works — google initiated contact for acp, jetbrains adopted it, claude code and codex and opencode and cursor all run inside zed. when the model vendors fight, the editor can host them all.", "id": "clm-proved-acp", "sourceIds": [ "src-hp-zed-acp", "src-hp-zed-jetbrains-acp", "src-hp-zed-claude-code", "src-hp-zed-codex", "src-hp-zed-10" ], "title": "agents come to the neutral surface" }the craft is credible · zed-idea-proved
Original location · source-8338fc8f0b5a04b0a867 · source-17626833242a03b0f32b · source-f9332b15b51417776c8a · source-82c476a7b5341d98687c
Original structured fields
{ "detail": "the team keeps its own credential — the people who built atom's collaboration stack wrote the crdt papers' production sequel, and the engineering blog ('zed decoded') became a respected rust publication independent of the product.", "id": "clm-proved-craft", "sourceIds": [ "src-hp-zed-team", "src-ci-zed-decoded-async", "src-ci-hn-async-rust", "src-hp-zed-craftsmanship" ], "title": "the craft is credible" }the post-commit world exists · zed-idea-proved
Original location · source-b1eaf0c240eb91f6ad9b · source-da3ae6d4dd42306c9587 · source-2687d4ddaa3bf8588b52
Original structured fields
{ "detail": "the second half of the plan exists in code — deltadb and delta shipped to public beta with pull requests disabled on the company's own repo: '33 of us have landed 570 changes to main' (self-reported). the memo idea from 2018 is a running product.", "id": "clm-proved-delta", "sourceIds": [ "src-hp-zed-deltadb", "src-hp-zed-delta", "src-hp-zed-delta-public" ], "title": "the post-commit world exists" }collaboration in the editor · zed-idea-stalled
Original location · source-4c037bbb714d9da82eec · source-ce36cc5f3be335ef5e12 · source-0e416df65a78b648674c · source-da3ae6d4dd42306c9587
Original structured fields
{ "detail": "collaboration inside the editor didn't stick — 'very few people leverage collab today' (company admission), the chat panel was removed wholesale, and channels survive as the office the team itself runs, not the product users adopted.", "id": "clm-stalled-collab", "sourceIds": [ "src-ci-gh-signin-issue", "src-ci-gh-remove-chat", "src-ci-zed-office", "src-hp-zed-delta" ], "title": "collaboration in the editor" }the extension gap · zed-idea-stalled
Original location · source-335be0c9128cb6cfa326 · source-2173a741602e44c625be · source-9c44f75dd5b99896093a
Original structured fields
{ "detail": "the extension gap persists — a deliberately conservative wasm api produced ~1,119 listed extensions mid-2026 against vs code's tens of thousands; 'my one plugin isn't there' remains the standard switching objection.", "id": "clm-stalled-extensions", "sourceIds": [ "src-hp-ghext-tracker", "src-ci-language-extensions", "src-hp-zed-extensions-decoded" ], "title": "the extension gap" }free ai · zed-idea-stalled
Original location · source-24595626e084d528bb75 · source-9925f88a6ff7facd76d3 · source-0fa4d1d1b2e607963fb4 · source-ecab0ff6bb1f245b1827
Original structured fields
{ "detail": "free ai didn't survive contact with the bill — free beta → at-cost billing → prompt bundles → token pass-through in eighteen months, each step read by some users as a smaller version of the same bait-and-switch.", "id": "clm-stalled-free-ai", "sourceIds": [ "src-hp-zed-ai-billing", "src-ci-pricing-token", "src-ci-hn-pricing", "src-hp-zed-ai-money" ], "title": "free ai" }gpui for everyone · zed-idea-stalled
Original location · source-f059142b43277b5502de · source-3cf0b8874a917a1ed57f · source-9da6ee0be604f87acc7e · source-cbe83a45ab27cd714954
Original structured fields
{ "detail": "gpui as a standalone framework stays aspirational — apache-2 and documented, but unpublished as a supported crate; the community (gpui-component, loungy, zedis, termy) builds on it anyway, which is evidence for and against the 'ui framework for everyone' claim.", "id": "clm-stalled-gpui", "sourceIds": [ "src-hp-gpui-rs", "src-ci-awesome-gpui", "src-ci-gpui-component", "src-hp-zed-gpui-ownership" ], "title": "gpui for everyone" }the ai trust ledger · zed-idea-stalled
Original location · source-ffde1f80e03767e91a62 · source-31a0cb59bbce0e5a47a4 · source-7c58c0ea0a1d59053a99 · source-1cc158b21f10714ee337
Original structured fields
{ "detail": "the ai-direction argument never fully closed — disable_ai shipped as a genuine concession, yet zedless exists and 'not much of an actual refutation' was the hn verdict on the economics defense.", "id": "clm-stalled-ai-debate", "sourceIds": [ "src-ci-disable-ai", "src-ci-zedless", "src-ci-hn-not-for-money", "src-ci-register-disable-ai" ], "title": "the ai trust ledger" }delta · zed-idea-successors
Original location · source-da3ae6d4dd42306c9587 · source-2687d4ddaa3bf8588b52 · source-bbc560cf27cba5f4ac78
Original structured fields
{ "href": "https://delta.dev", "id": "suc-delta", "name": "delta", "note": "the idea's own successor — the collaboration thesis grown into a separate product where threads replace pull requests. if it works, zed becomes the on-ramp, not the destination.", "sourceIds": [ "src-hp-zed-delta", "src-hp-zed-delta-public", "src-hp-delta-dev" ] }cursor · zed-idea-successors
Original location · source-9d6d1b0fcfbb163b1d54 · source-62a87ff2565b0c2a9b89
Original structured fields
{ "href": "https://cursor.com", "id": "suc-cursor", "name": "cursor", "note": "the opposite bet running at full speed — fork vs code, bundle the model, own the agent. the reference incumbent zed's neutral-surface strategy is defined against; cursor now also speaks acp.", "sourceIds": [ "src-hp-zed-10", "src-ci-hn-claude-code" ] }vs code + github · zed-idea-successors
Original location · source-5c85b6e328da996c46d8 · source-3836905382280c7c18bd · source-e2b799eee212ef0094c5
Original structured fields
{ "href": "https://code.visualstudio.com", "id": "suc-vscode", "name": "vs code + github", "note": "the incumbent stack zed has to displace twice — the editor monopoly atom's own electron enabled, plus the commit/pr workflow delta is built to replace. atom alumni now staff both sides.", "sourceIds": [ "src-hp-atom-oss", "src-hp-tc-atom-sunset", "src-hp-zed-start-over" ] }warp · zed-idea-successors
Original location · source-1b4d32c59b5cdbb48406
Original structured fields
{ "href": "https://www.warp.dev", "id": "suc-warp", "name": "warp", "note": "the road not taken — sobo's three-month employer built the agent workbench inside the terminal instead of the editor. same 'rebuild the tool for agents' impulse, different surface.", "sourceIds": [ "src-hp-zed-week1" ] }zedless · zed-idea-successors
Original location · source-31a0cb59bbce0e5a47a4 · source-e7e08cc016dd0e6ca4f2
Original structured fields
{ "href": "https://github.com/zedless-editor/zedless/", "id": "suc-zedless", "name": "zedless", "note": "the community fork as successor-with-an-asterisk — the editor thesis stripped of the company's services layer: no telemetry, no cla, no rugpulls. what gpl was always for.", "sourceIds": [ "src-ci-zedless", "src-ci-hn-zedless" ] }jetbrains + acp · zed-idea-successors
Original location · source-962c08be4137872f243e · source-3313f1a2152843b33046
Original structured fields
{ "href": "https://www.jetbrains.com", "id": "suc-jetbrains", "name": "jetbrains + acp", "note": "the protocol succeeding without zed — if acp becomes lsp-for-agents across the industry, the neutral-surface win outgrows the editor that minted it.", "sourceIds": [ "src-hp-zed-jetbrains-acp", "src-hp-zed-acp" ] }