agentboards.org
Compare/Cursor vs Zed

CursorvsZed

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

Cursor
Anysphere · AI-native IDE
#12MCP
Panel
6.8
2 spec wins
Reliability
7.0
Usefulness
7.7
Cost
5.5
Longevity
6.8

“Twenty dollars a month, then 3x, then 20x, and the page never says 20x of what.”

Zed
Zed Industries · AI-native IDE
#2OSSMCP
Panel
7.5
3 spec wins
Reliability
7.2
Usefulness
6.7
Cost
8.0
Longevity
8.0

“A GPL editor that will host Claude, Codex and Gemini in one panel, so the agent wars now happen inside a Rust window.”

Spec by spec

SpecCursorZed
Architecture
CategoryAI-native IDEAI-native IDE
Runslocal, cloudlocal
Platformsmacos, linux, windowsmacos, linux, windows
Context window200k default, up to 1M tokens on select modelsnot documented
Protocols
MCP clientYesYes
MCP serverNoNo
Capabilities
Runs terminal commandsYesYes
Multi-file editsYesYes
Git operationsYesYes
Browser controlYesNoThe agent's only web tools are fetch, which returns a URL as Markdown, and search_web; there is no browser control, Playwright or DevTools protocol access.
Sandboxed executionYesYesAgent tool calls run in an OS-level sandbox — Seatbelt via sandbox-exec on macOS and bubblewrap on Linux, applied to the terminal and fetch tools; on Windows only inside WSL.
Multi-agent orchestrationYesYes
Headless / CI modeYesNoThe zed CLI only opens files, windows and diffs — no print, exec or other non-interactive mode for running the agent from a script or CI is documented.
Models
BackboneClaude, GPT, Gemini, Grok, Composer, Kimi, GLMClaude, GPT, Gemini, Bedrock, OpenRouter, Ollama, LM Studio, Copilot
Bring your own modelYesYour own keys reach the vendors' own models (OpenAI, Anthropic, Google) plus your own Azure OpenAI deployment or AWS Bedrock account; Tab completion always stays on Cursor's models. Yes
Local modelsNoCustom API keys are limited to OpenAI, Anthropic, Google, Azure OpenAI and AWS Bedrock, with no documented base URL override, so Ollama, LM Studio or a self-hosted endpoint cannot be pointed at. Yes
Cost
Pricing modelmixedmixed
Starts at$20/mo$10/mo
Free tierYesYes
Bring your own keyYesYes
Openness
Open sourceNoYes
LicenseproprietaryGPL-3.0-or-later
GitHub starsn/a91,181

Which one would each critic pick

CriticCursorZedPick
El Juez——not enough reviews
El Amigo7.87.8no preference
El Crítico6.57.0Zed — The agent runs a terminal tool on your working tree with sandboxing off by default, and the fetch tool stays outside the sandbox even when you turn it on.
El Profesor6.07.3Zed — No benchmark claim, and an architecture worth studying: the Agent Client Protocol lets foreign agents run inside the editor, so the design does not depend on Zed's own loop.
La Inversora8.37.3Cursor — Real revenue, real pricing power, an in-house model, and a dependency on the labs it competes with for every frontier request.
La Jefa7.56.5Cursor — Teams at $40 per user with SSO, but SCIM, audit logs and auto-run controls sit behind a custom Enterprise quote.
El Hacker4.59.0Zed — GPL-3.0, MCP servers in a context_servers block in settings.json, Ollama and LM Studio as providers, and ACP to plug my own agent in.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.