86 sources from practitioners, by month and sentiment.
Across public accounts, praise centers on the Zed Agent and on running other agents and models inside a fast editor. The most frequent concern is that Claude Code, Codex, and other ACP agents lose features inside Zed. Engineers who rely on tab completion keep going back to Cursor.
Positive, mixed and negative sources
262011
The score counts them as 25 positive, 20 mixed and 11 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 86 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Zed Agent and Review Flow16 of 17 sources on it praise itZed's own agent, its ask and write modes, parallel threads, and reviewing agent edits in the editor.
Sees a useful review loop in which a coworker inspects an agent thread directly and needs no explanation from its author, though they want polished final output.
Published Sep 18, 2026self-described: Response to a video of Zed collaborative review
Practitioner account, pseudonymous; opinion; not counted, takes no position
Loves Zed with OpenRouter at home but finds its Claude Code integration weak next to the Zed Agent with a Claude model, so uses VS Code with Claude Code at work.
Published Apr 22, 2026self-described: Developer using Zed at home and Claude Code at work
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
travisgriggs, Hacker News commenter at a 2-3 person shop
Was blown away by Zed's agent as a first coding agent, moved to Claude Code weeks later, and canceled the 20 EUR per month subscription for AI features no longer used.
Published Sep 4, 2025self-described: Developer describing their own use of Zed's AI features
Uses ask mode to discuss approaches and draft patches, then write mode to implement and run tests and diagnostics, then a line-by-line review before a pull request.
Published Aug 5, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; counts toward Operational control
Runs each task in the agent panel: plans with Claude 4 Sonnet in thinking mode, then switches to Sonnet 4 in the same conversation to implement, then reviews and tests.
Published Jul 21, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; counts toward Operational control
Valim credits Zed with an excellent job of bringing editor diagnostics and code actions into its agentic workflows, while most agent tools still see only the code as written.
"The Zed editor also does an excellent job at integrating some editor features, such as diagnostics and code actions, into their agentic workflows."
Excerpt, José Valim
Published Jun 6, 2025Introducing Tidewave, Dashbit's runtime-aware tools for coding agents
Practitioner account, name and role on an outside page; opinion; not counted, takes no position
After a few days with Zed's new AI features, Mota found the Agent Panel pretty nice but short on polished defaults, and edit predictions never appeared. He still wants Zed as his default but flips back to Cursor when he hits an issue.
"Despite all the quirks, I still find myself wanting to default to it, but then flipping back to Cursor when I run into an issue."
Excerpt, Victor Mota
Published May 10, 2025Trying Zed's new AI features against Cursor, including on his team's Python monorepo
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Finds the new agent panel does the right thing more often than Cursor or Windsurf. It gathers the right context, asks for feedback when needed, and has not looped between two failing fixes.
Published May 7, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
2Claude Code and Other Agents in the EditorAll 12 sources on it praise itRunning Claude Code, Codex, Gemini CLI, OpenCode, or another agent in Zed's panel through the Agent Client Protocol.
Counted for All practitioners.
Positive
Jacob Wolf, leads podcasts and integrations engineering at beehiiv
Is leaving JetBrains because its bundled AI is not worth paying for beside Claude Code, and finds Zed's Claude Code integration richer than JetBrains'.
Published Jan 5, 2026self-described: Developer leaving a JetBrains subscription after nearly 10 years
Practitioner account, pseudonymous; direct use; not counted, takes no position
Valim uses Zed a lot alongside Tidewave, waiting on their notifications while agents work, and says Tidewave is building on Zed's ACP to talk to Codex, Claude Code and Gemini CLI. Thinks pushing people to build on Claude Code or Codex "like with ACP" is "not actually a bad idea".
"I actually think pushing people towards using Claude Code more, or Codex, and building on top of those tools, like with ACP, is not actually a bad idea…"
Excerpt, José Valim
Published Oct 10, 2025Creator of Elixir, building Dashbit's Tidewave coding agent on ACP
Practitioner account, name and role on an outside page; direct use; not counted, takes no position
McAdam switched to Zed as his IDE while OpenCode writes the code, and uses Zed to clean up code and review large files and plans, calling it clean and light.
"…switched to Zed as my ide @opencode writes everything Zed is for cleaning up code, reviewing large files/plans…"
Excerpt, Omar McAdam
Published Apr 29, 2026CTO of Different AI, which builds OpenWork, with OpenCode as his coding agent
Practitioner account, pseudonymous; direct use; not counted, takes no position
McQuaid runs Codex and Claude Code in sandboxed worktrees and edits their output in Zed, his editor of choice, picked for startup speed because he no longer needs Cursor's better autocomplete.
"I picked Zed because I spend less time in my editor now, don’t need Cursor’s better autocomplete and care more about startup speed…"
Excerpt, Mike McQuaid
Published Apr 14, 2026Runs sandboxed Codex and Claude Code agents on Homebrew and Administrate repositories
Practitioner account, self-described; direct use; not counted, takes no position
Calls Zed really nice, with awesome simplicity and speed and LSP servers used directly. Amp cutting editor-specific layers such as VS Code extensions led the author to Zed; setting up Amp's codebase took about 30min, and the author will be trying it out this week.
"But we're reducing our reliance on human-only/in-editor feedback loops in our codebase, because the ones used by agents are more important."
Excerpt, Quinn Slack
Published Feb 10, 2026Moving Amp's own codebase toward feedback loops that coding agents use
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Left VS Code over intrusive Copilot features. Found Zed fast and responsive, with no stability problems in two weeks. Uses Codex in the CLI for AI work.
Published Jan 3, 2026self-described: Python and Go developer who uses a CLI agent (Codex) for AI work
Practitioner account; direct use; counts toward Reliability, Adoption and upkeep
Prefers Zed because the developer keeps control over API calls, where Cursor spent the API quota unexpectedly, and because Zed matches Sublime's speed.
Published May 7, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After a few days with Zed's new AI features, Mota found the Agent Panel pretty nice but short on polished defaults, and edit predictions never appeared. He still wants Zed as his default but flips back to Cursor when he hits an issue.
"Despite all the quirks, I still find myself wanting to default to it, but then flipping back to Cursor when I run into an issue."
Excerpt, Victor Mota
Published May 10, 2025Trying Zed's new AI features against Cursor, including on his team's Python monorepo
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
4Model and Provider ChoiceAll 7 sources on it praise itBringing your own key, a local model, OpenRouter, or a company tenant, and switching models per task.
Loves Zed with OpenRouter at home but finds its Claude Code integration weak next to the Zed Agent with a Claude model, so uses VS Code with Claude Code at work.
Published Apr 22, 2026self-described: Developer using Zed at home and Claude Code at work
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
Ewan (kisamoto on Hacker News), author of Braw.dev
Trusts Zed more since its AI plans began, because Pro buys tokens across OpenAI, Anthropic, and Google with a spending cap, which looks like a sustainable business model.
Published Jan 5, 2026self-described: Early Zed adopter
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Runs each task in the agent panel: plans with Claude 4 Sonnet in thinking mode, then switches to Sonnet 4 in the same conversation to implement, then reviews and tests.
Published Jul 21, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; counts toward Operational control
Prefers Zed because the developer keeps control over API calls, where Cursor spent the API quota unexpectedly, and because Zed matches Sublime's speed.
Published May 7, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Trusts Zed more since its AI plans began, because Pro buys tokens across OpenAI, Anthropic, and Google with a spending cap, which looks like a sustainable business model.
Published Jan 5, 2026self-described: Early Zed adopter
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
travisgriggs, Hacker News commenter at a 2-3 person shop
Pays for Zed Pro only for edit prediction and calls it garbage next to Cursor's, though the 10 to 20% of useful suggestions still justify the subscription.
Published Sep 24, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Every concern practitioners raise, most raised first.
1External Agents Lose FeaturesAll 17 sources on it raise it as a concernClaude Code, Codex, Gemini CLI, and other ACP agents missing commands, history, hooks, subagent displays, or context controls they have in their own apps.
A Zed user who says Claude Code in the panel is not really Claude Code: ACP reduces the agents to shared functionality, with very limited context management.
Published Oct 18, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Praises Zed's speed and diff review, but after 30 days of standalone Claude Code finds the beta integration a step back, without Plan Mode, /compact, or subagents.
Published Sep 6, 2025self-described: Builds internal tools for retail, education, and B2B teams at C&C, an Apple Premium Partner
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control
Loves Zed with OpenRouter at home but finds its Claude Code integration weak next to the Zed Agent with a Claude model, so uses VS Code with Claude Code at work.
Published Apr 22, 2026self-described: Developer using Zed at home and Claude Code at work
Practitioner account, pseudonymous; direct use; not counted, takes no position
GILD's fact checks, which don't count as sources
Checked Oct 25, 2026.Zed's documentation states that some Agent Panel features, including history, checkpoints, and token usage display, depend on each external agent's integration. Agent Panel
2Crashes, Freezes, and SlowdownsAll 9 sources on it raise it as a concernPanics, frozen threads, slow agent runs, and high CPU, memory, or energy use while agents run.
Reports that GPT-5.3 Codex through the GitHub Copilot provider is unusable in Zed 0.223.5: tool calls often fail, it says it edited files without editing anything, and it stops before doing the work. Other Codex models work well in Zed.
Published Mar 3, 2026self-described: Using GPT-5.3 Codex from a GitHub Copilot subscription in the Zed Agent
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
3Agent Panel and LayoutAll 7 sources on it raise it as a concernConfusing agent controls, an agent-first layout that crowds out code, or an agent that acts before it is asked.
After a few days with Zed's new AI features, Mota found the Agent Panel pretty nice but short on polished defaults, and edit predictions never appeared. He still wants Zed as his default but flips back to Cursor when he hits an issue.
"Despite all the quirks, I still find myself wanting to default to it, but then flipping back to Cursor when I run into an issue."
Excerpt, Victor Mota
Published May 10, 2025Trying Zed's new AI features against Cursor, including on his team's Python monorepo
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
4Token Markup and Subscription ValueAll 6 sources on it raise it as a concernHosted tokens billed above the providers' own prices, per-token costs that are hard to work out, or a subscription paid for AI the developer stopped using.
Has looked at Zed editor's default prompt and thought "I hope this is worth the 7k tokens it costs me every session", and suggests "perhaps" the takeaway is to beware overly long prompts and keep the system prompt relevant to the field of work.
Published Sep 17, 2026self-described: Zed editor prompt overhead
Practitioner account, pseudonymous; direct use; not counted, takes no position
No opinion stated
kisamoto (Ewan), author of the Braw.dev post under discussion
Says that "sadly Zed seems to add 10%", so it is still more worthwhile to use OpenRouter, and that it is "perhaps" more worthwhile to stay solely on Cursor with the limited models.
Published Apr 9, 2026self-described: Developer moving a US$100 per month Claude Code budget to Zed and OpenRouter
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Positive
Ewan (kisamoto on Hacker News), author of Braw.dev
Was blown away by Zed's agent as a first coding agent, moved to Claude Code weeks later, and canceled the 20 EUR per month subscription for AI features no longer used.
Published Sep 4, 2025self-described: Developer describing their own use of Zed's AI features
not counted, repeats a stronger account
GILD's fact checks, which don't count as sources
Checked Oct 25, 2026.Zed bills hosted model usage at API list price plus 10% after Pro's included US$5, with an optional spending cap. Your own keys and external agents bill through their providers. Zed pricing
5Edit Predictions Trail Cursor Tab6 of 8 sources on it raise it as a concernZeta and other edit prediction providers in Zed suggesting less useful or less far-reaching edits than Cursor's tab completion.
Pays for Zed Pro only for edit prediction and calls it garbage next to Cursor's, though the 10 to 20% of useful suggestions still justify the subscription.
Published Sep 24, 2025self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Found Zed more responsive than VS Code and loved the Zed Agent autocomplete, then went back to VS Code over a debugger bug.
Published Apr 9, 2026self-described: Developer describing their own use of Zed's AI features
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
GILD's fact checks, which don't count as sources
Checked Oct 25, 2026.Zeta is included on Pro, the Pro trial, and the Student and Business plans. Copilot, Codestral, Mercury Coder, or a local model can serve predictions instead. Edit Prediction
6AI Depth Behind CursorAll 5 sources on it raise it as a concernZed's AI features trailing Cursor's agents, background agents, and developer experience.
Questions the sources split on, with the count on each side.
Evidence remains mixed
Should engineers work with the Zed Agent or bring an external agent?
621
Zed Agent, 6 sources
Some prefer Zed's own agent with a chosen model, for its review flow and its tighter fit with the editor.
External agent, 21 sources
Others run Claude Code, Codex, or another agent, in Zed's panel or in a terminal, and treat Zed as the place to read and edit code.
Evidence remains mixed
Should AI in Zed run on Zed's hosted plan or on your own key?
58
Zed's hosted plan, 5 sources
Some pay for Zed Pro for edit predictions and hosted tokens, and see it as fair value that also funds the editor.
Own key or subscription, 8 sources
Others route models through their own provider, OpenRouter, a company tenant, or an agent subscription, to avoid Zed's markup.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 11 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
18 sources. These accounts emphasize bring-your-own-key buying, which external agents a team may run, and how far the Zed Agent and ACP agents match the tools engineers already use.
Individual builders
68 sources. These accounts emphasize edit prediction quality, the Zed Agent, Claude Code and Codex over ACP, model choice, and what AI in Zed costs one developer.
All practitioners
86 sources. These figures count every account: individual developers and the team and leadership accounts together.
86 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders68 sources, counted here
Emphasizes Edit predictions, the Zed Agent, and Claude Code over ACP in one developer's day
Very small team2 to 10 engineers, or a team of unstated size1 sources, counted here
Emphasizes Whether Zed Pro and the integrated agent earn their place in a small shop
Professional team11 to 50 engineers, or a named company's team1 sources, counted here
Emphasizes Whether Claude Code in Zed matches the standalone tool for production work
Technical leadershipLeaders setting adoption across teams16 sources, counted here
Emphasizes Own-key buying and how external agents behave in the panel
Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual developers argue about edit predictions and which agent to run. Leaders and named-company accounts turn to buying and integration: whether model traffic can stay on the company's own key, and whether Claude Code and Codex keep their features inside Zed.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 86 sources. Change group
95 sources for this group, 9 of them documentation
Developer Communities82, 86% of 95 sources
Product Documentation9, 9% of 95 sources
Engineering Blogs & Reviews3, 3% of 95 sources
Talks & Podcasts1, 1% of 95 sources
Older evidence is retained when it still applies. Accounts of the launch-day agent panel, the Claude Code and Codex betas, and closed issues stay in the history, marked Needs a recheck.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Zed now casts no vote; it still counts toward its topics and is listed, and 23 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +27 to +22 and all practitioners from +29 to +25.
Oct 31, 2026: rewrote 9 summaries that two blind coders found overstated their sources, so each says what its source says. Five comments state no view of Zed overall and now carry no sentiment, and two no longer praise model choice. GitHub issues still count as mixed, as the method says. Individual builders move from +26 to +27 and all practitioners from +41 to +39.
Builds the Zed evidence base from public pages: each account names its author and publication date and is coded from an exact quote on the page.
Shows a finding only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Counts the Braw.dev post and its author's Hacker News reply as one author.
Oct 26, 2026: adds named CTOs and founders at Icehouse Ventures, Different AI, Administrate, Dashbit, Paper, Supermemory, Amp and CoPlane, each role as stated on the person's own or their company's site.
Method
A running review of what engineering teams report about Zed, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +39 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +41 Positive; with one vote per author it read +28 Positive. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +29 Positive and now reads +25 Positive.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 2 of 11, individual builders 2 of 46, all practitioners 4 of 57.
Limits
These figures count 86 public accounts: 55 Hacker News comments, 7 issues on zed-industries/zed, 6 blog posts, 17 posts on X, and a podcast transcript, plus 9 Zed documentation pages. Hacker News comments come from the threads under Zed's own AI announcements, which draws in people already weighing Zed against Cursor and Claude Code. GitHub issues are bug reports and count as mixed. Reddit refused access to the threads GILD found, so none is in this record. Team and leadership accounts come mostly from named CTOs and founders whose roles appear on their own or their company's pages. None describes an organization-wide rollout. This is not a representative survey.
The record runs from the agent panel launch in May 2025 through Zed 1.0 in April 2026 and the 1.x releases after it. Accounts tied to a launch-day build or a closed issue are marked Needs a recheck.
Every count, and the sources behind it
18 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
External Agents Lose Features. Zed's documentation states that some Agent Panel features, including history, checkpoints, and token usage display, depend on each external agent's integration. Agent Panel, checked Oct 25, 2026
Edit Predictions Trail Cursor Tab. Zeta is included on Pro, the Pro trial, and the Student and Business plans. Copilot, Codestral, Mercury Coder, or a local model can serve predictions instead. Edit Prediction, checked Oct 25, 2026
Token Markup and Subscription Value. Zed bills hosted model usage at API list price plus 10% after Pro's included US$5, with an optional spending cap. Your own keys and external agents bill through their providers. Zed pricing, checked Oct 25, 2026