Agentic Index
Cursor vs Zed (2026)
Cursor last verified ·Zed last verified
Cursor is the deeper AI platform and Zed is the faster editor. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Cursor leads on agent orchestration, enterprise controls, and ecosystem, built on a familiar VS Code base. Zed, written in Rust by the team behind Atom, wins on raw speed, native collaboration, and openness, with a $10 Pro tier and support for fifteen model providers.
On the Agentic Index coding agent ranking, neither Cursor nor Zed clears the bar, which asks for all five merge loop capabilities documented in full. Cursor does not document knowledge grounding and RAG in full, nor testing, debugging and optimization; Zed documents two of the five in full. 3 of the 96 vendors in the lane clear it. See the coding agent ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Cursor and Zed are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,140 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Cursor if
- Agent capability is the priority, with parallel background agents, an Agents Window, and in house models tuned for agentic coding.
- You depend on the VS Code extension ecosystem and want your existing setup to carry over.
- You need enterprise features shipped today, including Privacy Mode enforced organization wide.
Choose Zed if
- Editor speed matters every minute of the day. GPU rendering makes scrolling, search, and keystrokes feel instant.
- You pair and review in real time. Multiplayer editing, voice, and screen sharing are native, not plugins.
- You want openness, with open source under Apache, local models through Ollama, and external agents plugged in through the Agent Client Protocol.
| Feature | C Cursor |
Z Zed |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
CursorIntegrations & Tool Calling MCP servers connect the agent to external tools and data over stdio, SSE or Streamable HTTP with OAuth for remote servers, installed one click from the Cursor Marketplace or configured in mcp.json, and team admins can distribute servers through a team marketplace; tools, prompts, resources and elicitation are supported. Sourcecursor.com/docs/mcpread 2026-09-29 |
||
|
ZedIntegrations & Tool Calling A native first-party agent runs with built-in tools, while external agents including Claude Agent, Codex, Copilot, Cursor, Gemini CLI and OpenCode connect through the open Agent Client Protocol. Terminal Threads run any command line agent as a persistent sidebar, and MCP servers extend agent tools and knowledge. The editor itself provides first-class Git operations for staging, committing, pushing and diffs, native debugging through the Debug Adapter Protocol, language server support, roughly 800 extensions, and remote development over SSH. Context is added by mentioning files, directories, symbols, diagnostics, branch diffs, previous threads and fetched URLs. Sourcezed.dev/ai, zed.dev/docs/ai/mcp and zed.dev/extensionsread 2026-08-30 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
CursorWorkflow Orchestration The agent delegates to subagents that each run in their own context window, in the foreground or in the background and in parallel, with built in Explore, Bash and Browser subagents and custom subagents defined with their own prompts, tool access and models, in the editor, the CLI and Cloud Agents. Sourcecursor.com/docs/subagentsread 2026-09-29 |
||
|
ZedWorkflow Orchestration The spawn_agent tool in Zed Agent starts a subagent with its own context window for a delegated task, such as a parallel investigation while the parent continues and then reviews the findings. Parallel agent threads and Terminal Threads run at once from the Threads Sidebar across projects, with Git worktrees isolating each thread's changes. Sourcezed.dev/docs/ai/tools and /docs/ai/parallel-agentsread 2026-09-29 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
CursorTriggers & Channel Coverage Automations run cloud agents in the background on a schedule (preset or cron) or in response to events, a GitHub pull request opened or marked ready, Slack messages, Linear issue changes, PagerDuty incidents, Sentry errors and webhooks, with no person starting the run; Bugbot also reviews every pull request update automatically. Sourcecursor.com/docs/cloud-agent/automations and docs/bugbotread 2026-09-29 |
||
|
ZedTriggers & Channel Coverage Zed runs natively on macOS, Linux and Windows with the AI features reached from the Agent Panel inside the editor, alongside a Threads sidebar, Terminal Threads running command line agents persistently, inline assistance in the buffer, remote development over SSH against a codebase held on a server, and real-time collaboration sessions where multiple humans and the agent share the same workspace. The developer starts work by typing in the message editor or invoking inline assistance. There is no event-driven trigger, scheduled run or inbound chat or ticketing channel. Sourcezed.dev/ai and zed.dev/docs/ai/agent-panelread 2026-08-30 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
CursorKnowledge Grounding & RAG The agent finds code with Instant Grep, an exact match and regex search engine that builds and queries its index on the developer's machine, and an Explore subagent that runs parallel searches per task; files, folders and past chats are attached per conversation with @ mentions. Cursor does not store embeddings of the codebase for search, so context is gathered on each run, and the local grep index exists to speed up search. Sourcecursor.com/docs/agent/tools/search and help/customization/contextread 2026-09-29 |
||
|
ZedKnowledge Grounding & RAG The agent searches the codebase for relevant context during a task, and developers add context by mentioning files, directories, symbols, diagnostics, branch diffs, previous threads and fetched URLs, with multi-core indexing and language servers making retrieval fast. Agent Profiles, Skills and Instructions carry standing project guidance, and thread history can be restored as context. There is no repository index product, semantic retrieval layer, dependency graph or cross-file reasoning surface, and project-wide context depends heavily on what the developer passes in. Sourcezed.dev/docs/ai/agent-panel and zed.dev/docs/ai/overviewread 2026-08-30 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
CursorMemory & State Persistence Past agent transcripts can be searched from the Agents Window and attached to a new conversation with @Chats, and checkpoints snapshot modified files within a session. Cursor does not describe a memory layer of its own, project rules act as standing instructions, and subagents start without prior conversation history. Sourcecursor.com/help/customization/context and docs/agent/overviewread 2026-09-29 |
||
|
ZedMemory & State Persistence A checkpoint system reverts the workspace to the state before any edit batch, and threads can be restored from history so a session can be resumed later, though these features depend on the agent integration and vary across external agents. Agent Profiles, Skills and Instructions persist as configuration the customer writes and the agent reads on every run, and parallel Git worktrees hold isolated state per agent thread. There is no memory layer that builds up learned context, preferences or corrections across sessions. Sourcezed.dev/docs/ai/agent-panel and zed.dev/docs/ai/overviewread 2026-08-30 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
CursorHuman Oversight & Guardrails Run Modes decide when the agent stops for approval on shell, MCP and fetch calls: Allowlist runs only listed actions without asking, Auto-review sandboxes shell commands and sends other calls to a classifier that can ask the user to approve, plain English block instructions route named actions to approval, and a team configuration set in the dashboard overrides user and project settings; browser tools require approval by default. Sourcecursor.com/docs/agent/security/run-modes and docs/agent/tools/browserread 2026-09-29 |
||
|
ZedHuman Oversight & Guardrails Tool approval is set through agent.tool_permissions. It has a global default of allow or confirm, per-tool defaults, always_allow patterns, always_confirm patterns that prompt case by case (for example sudo commands) regardless of other settings, and auto-deny rules for dangerous actions that hold even when the default is allow. Zed Agent tool calls can also run in an OS-level sandbox. After a run the developer reviews changes in an editable unified diff, accepting or rejecting each, and checkpoints revert any edit batch. Sourcezed.dev/docs/ai/tool-permissions, /docs/ai/sandboxing and /docs/ai/agent-panelread 2026-09-29 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
CursorSecurity, Identity & Governance Cursor holds a SOC 2 Type II attestation and AIUC-1, ISO/IEC 27001:2022 and ISO/IEC 42001:2023 certifications, with certificates and reports available on request at trust.cursor.com, and offers SSO, SCIM and enforced multi factor authentication. SAML and OIDC SSO come on Teams, and SCIM, repository and model access controls and audit logs on Enterprise. Sourcecursor.com/security and cursor.com/pricingread 2026-09-29 |
||
|
ZedSecurity, Identity & Governance Work toward SOC 2 Type 1 certification is under way, and SSO, SAML and SCIM are planned but not available. The Business admin layer is shipped, with organization roles and permissions, org-wide AI model policies, data governance controls and unified spend visibility, and local and bring-your-own-key paths keep code away from Zed. Sourcezed.dev/docs/soc2, /docs/roles and zed.dev/pricingread 2026-09-29 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
CursorObservability & Auditability Hooks fire on every step of the agent loop (preToolUse and postToolUse, shell and MCP execution before and after, file reads and edits, subagent start and stop, agent responses and thoughts), auditing is one of their named uses, and Enterprise admins distribute team hooks from the dashboard. The Admin API returns per request usage events with model, tokens and conversation ID, and its audit log covers logins and user and settings changes, with no agent actions among them. Cursor does not ship a log sink for the per step hook record, so the customer builds one to keep that record as an audit trail. Sourcecursor.com/docs/hooks and docs/account/teams/admin-apiread 2026-09-29 |
||
|
ZedObservability & Auditability Developers follow the agent live as it navigates the codebase, using the same multiplayer infrastructure that powers human collaboration, with responses streaming and indicators showing which tools the model is using. Token usage is displayed, threads can be restored from history, and unified spend visibility is available to teams on Business. Zed publishes public agent metrics comparing usage across Zed Agent, Claude Agent and Codex CLI over rolling windows. Thread history, checkpoints and token display depend on the agent integration and vary for external agents. There is no retained per-action execution trace, audit log or replay. Sourcezed.dev/docs/ai/agent-panel, zed.dev/agent-metrics and zed.dev/businessread 2026-08-30 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
CursorDeployment & Data Residency Self-Hosted Machines move Cloud Agent tool execution to machines the customer manages, such as a Linux VM in the customer's AWS account, a Kubernetes cluster or its own devices, with the checkout, build cache and machine local credentials staying there (Team Pools on Enterprise). Cursor still runs the agent loop, inference and planning, and Enterprise customers can enroll in US only data residency. Sourcecursor.com/docs/cloud-agent/self-hosted and help/security-and-privacy/regionsread 2026-09-29 |
||
|
ZedDeployment & Data Residency Zed is open source under Apache 2.0 and runs as a native application on macOS, Linux and Windows entirely on the developer's own machine, with the source publicly cloneable. Local models run through Ollama or LM Studio, and Zed says nothing leaves the machine. Bring your own key sends data directly to the customer's chosen provider, not through Zed, and the Zeta edit-prediction model is open-weight, with self-hosted Next Edit models supported. Remote development keeps the codebase on a server the customer controls while the local machine runs only the interface, and the editor works fully without AI features or any signed-in account. Sourcezed.dev/ai, zed.dev/docs/ai/llm-providers and zed.dev/edit-predictionread 2026-08-30 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
CursorPrebuilt Agents, Templates & Packs Plugins bundle rules, skills, agents, commands, MCP servers and hooks, and the Cursor Marketplace lists manually reviewed official plugins installed per project or user from Customize, including Amplitude, Datadog, Figma, Linear, Sentry, Stripe, Supabase and Vercel plugins. Teams and Enterprise can run private team marketplaces, and three subagents ship built in. Sourcecursor.com/docs/plugins and cursor.com/marketplaceread 2026-09-29 |
||
|
ZedPrebuilt Agents, Templates & Packs The ACP Registry is the primary way to install External Agents. It opens from the command palette or Agent Settings and lists ready agents such as Claude Agent, Codex, Gemini CLI, OpenCode, Copilot, Cursor and Pi Coding Agent, and an installed agent appears in the new-thread menu. Agent Server Extensions publish further agents through the Zed Extension Registry, and Zed Agent is shaped by reusable Agent Profiles, Skills and Instructions. Each agent in the registry installs in one step. Sourcezed.dev/docs/ai/external-agents and /docs/extensions/agent-serversread 2026-09-29 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
CursorModel Flexibility & Routing Cursor's own models, Grok and Composer, run from a weekly usage pool on every paid plan. On Premium and above, users also pick Anthropic, OpenAI and Google models at API list price from prepaid credit. On Teams and Enterprise, Cursor Router picks among Cursor and third party models by cost, balance or intelligence, and admins allow or block models. Plus is limited to Grok models. Sourcecursor.com/docs/models-and-pricing and cursor.com/pricingread 2026-10-25 |
||
|
ZedModel Flexibility & Routing There are three model paths. Zed-hosted models, including Claude Opus and GPT 5.4, need no API keys to manage, local models run through Ollama and Zed says nothing leaves the machine, and bring your own keys works with any provider using the customer's existing accounts and budgets, with LM Studio also supported. Fifteen providers are supported, including Anthropic, OpenAI, Google, Amazon Bedrock, Mistral, OpenRouter and Vercel, and merged community contributions continue to add providers and models including Gemini 3.7 Flash and OpenRouter effort-based reasoning. The Zeta edit-prediction model is open-weight and self-hostable, with self-hosted Sweep Next Edit models also supported. Sourcezed.dev/ai, zed.dev/docs/ai/llm-providers and zed.dev/edit-predictionread 2026-08-30 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
CursorAPIs, SDKs & MCP Extensibility The Cloud Agents API at api.cursor.com, with Basic or Bearer authentication on user or service account keys, creates, lists, follows up, streams, cancels, archives and deletes agents and their runs and returns artifacts, and TypeScript and Python SDKs are published beside it. Sourcecursor.com/docs/cloud-agent/api/endpointsread 2026-09-29 |
||
|
ZedAPIs, SDKs & MCP Extensibility The Agent Client Protocol, which Zed authored and publishes, is an open standard with its own site for connecting any agent to any client. Zed, the Zeta model and ACP are all open source and built in public. The editor is Apache 2.0 with a public repository, a defined extension interface and roughly 800 published extensions, MCP server support extends agent tools and knowledge, and Tool Permissions expose settings for what those tools may do. Community contributions to the AI subsystem are merged continuously and listed publicly, including provider additions and agent model updates. Sourcezed.dev/acp, zed.dev/ai and zed.dev/extensionsread 2026-08-30 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
CursorTesting, Debugging & Optimization Bugbot reviews each pull request for bugs, security issues and quality problems and publishes a CI check status, and a custom verifier subagent can run the tests and report what passed. Both test the customer's code, and Cursor does not describe a harness, scored test set or optimization loop for evaluating the agent's own behavior. Sourcecursor.com/docs/bugbot and docs/subagentsread 2026-09-29 |
||
|
ZedTesting, Debugging & Optimization Native multi-language debugging is built in through the Debug Adapter Protocol, language servers surface diagnostics that can be mentioned as agent context and acted on, and the agent runs tests and other commands as tools within the workspace, with results visible as it works. Zed publishes editor performance benchmarks and a public agent metrics page comparing how developers use different agents, but both measure Zed and the ecosystem and are not a harness the customer points at agent behavior. There is no test generation, evaluation or regression testing product. Sourcezed.dev/ai and zed.dev/docs/ai/agent-panelread 2026-08-30 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
CursorBrowser & Computer Use The browser tool lets the agent control a browser pane inside Cursor, navigating, clicking, typing, scrolling and taking screenshots to test applications, audit accessibility and check visual changes, through Cursor's own MCP server, with approval required by default and an admin origin allowlist; a built in Browser subagent runs these steps, and self hosted workers run computer use tools. Sourcecursor.com/docs/agent/tools/browser and docs/subagentsread 2026-09-29 |
||
|
ZedBrowser & Computer Use The agent works through programmatic surfaces throughout, file reads and edits in the workspace, tool calls governed by the Tool Permissions system, MCP servers, Terminal Threads running command line processes, native debugging through the Debug Adapter Protocol, language servers, and Git operations. There is no browser control, screenshot capture, visual verification or way to operate software that lacks a programmatic interface. External agents connected over ACP may carry their own browser tooling, which belongs to those agents, not to Zed. Sourcezed.dev/ai and zed.dev/docs/ai/agent-panelread 2026-08-30 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | C Cursor |
Z Zed |
|---|---|---|
|
Entry price Lowest public entry point |
Free plan, Plus at $8 a month with Grok models only, Premium at $30 a month, Super at $100, Ultra at $200, Teams from $30 per user a month, and Enterprise at custom pricing. | Personal is free forever, with unlimited use of your own keys, external agents and local models. Pro is $10 a month for unlimited edit predictions plus $5 of hosted model credit, with hosted usage beyond it at provider list price plus 10 percent. Business is $30 per seat, with hosted AI billed at standard usage rates. |
|
Pricing confidence How public the numbers are |
Public, partial | Public, exact |
|
Billing Primary billing axis |
A monthly plan with a weekly usage pool for Cursor's own models, Grok and Composer. Models from other makers are paid from prepaid credit at API list price on Premium and above. | A free editor that runs on the customer's own keys, external agents or local models, then a low flat subscription. Pro adds unlimited edit prediction and a small hosted model credit, after which hosted usage is billed by tokens at the provider's list price plus ten percent, and Business seats bill hosted AI at standard usage rates. Bringing your own key or running local models avoids that usage cost entirely. |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
Free tier
|
Free tierTrial
|
|
Buying motion Self-serve vs sales call |
Mixed | Self-serve |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Cursor
-
· Agent capability
Realtime voice calls with agents now work in the Cursor IDE and on the web, alongside the Agents Window and the iOS app.
Source -
· Agent capability
Cloud agents in Cursor can now build and publish live web apps.
Source -
· Human approval / guardrails
Cursor 3.24 makes Auto-review stop for approval before the agent runs a recursive, force, wildcard or mirror delete whose target could resolve differently than written, and commands that match a user's block instructions now always show the approval card.
Source
Zed
-
· Human approval / guardrails
Agent checkpoints and the Restore Checkpoint button are gone from the Agent Panel in Zed 1.27.0 on the Stable channel.
Source -
· Agent capability
Context compaction and session notices now work for external agents that connect to Zed over the Agent Client Protocol (ACP), starting with release 1.25.2.
Source -
· Workflow orchestration
A parent agent in Zed 1.22.0 can now choose the model for each subagent it spawns instead of using one configured subagent model, and subagents now compact their context when it fills up.
Source
More comparisons with Cursor or Zed
Other matchups in coding agents
Not the pairing you were after? These compare a different set of coding agents on the same 14 capabilities.