Agent Metrics
Anonymized, aggregated performance data from developers using AI agents through Zed.
Last updated: July 13th, 2026Group metrics
Time range
Sort by
Agents
Most Popular Agents
Here's how weekly are trending across the selected agents, over the last 30 days. Explore full methodology →
Total Sessions
935.5KTotal Turns
7.4M| 1 | 378,416 | ||
| 2 | 319,716 | ||
| 3 | 112,969 | ||
| 4 | 70,650 | ||
| 5 | 19,287 | ||
| 6 | 14,133 | ||
| 7 | 7,821 | ||
| 8 | 6,510 | ||
| 9 | 3,801 | ||
| 10 | 2,243 |
Fastest Agents
Compare response-time distributions across the selected agents. Explore full methodology →
Local Models in the Mix
Local models run entirely on your device, as opposed to cloud-hosted ones. Learn more →
Local Sessions
22.5KLocal Turns
90.5KCross-ecosystem by design
Developers can bring any AI agent they want to Zed (we think of ourselves as the "Switzerland" of editors). Many agents connect through ACP, the Agent Client Protocol, a shared open standard for agent-editor communication.
This means we see agent usage across the ecosystem, not just our own. We can offer a more comprehensive view of how AI agents are actually used than most editors can — or would.
Frequently Asked Questions
Anonymized and aggregated data from users interacting with the Zed agent and other agents via the Agent Client Protocol. No individual user data is exposed.
We re-pull data weekly. This allows time for new models to accumulate meaningful sample sizes.
We only show agents that have sufficient data to report meaningful metrics. Agents with very low usage within Zed may not appear.
No. This is aggregated, anonymized data. We do not track or expose individual user metrics.
Turn time depends on model configuration, context window size, task complexity, and infrastructure factors. These metrics show aggregate trends, not guarantees.
Methodology
The metrics on this page are derived from anonymized, aggregated telemetry collected from Zed users who interact with AI agents. No individual session data, user identifiers, or proprietary code is exposed, and all data is aggregated before display.
-
What we collect: When you use an AI agent in Zed, we record metadata about the interaction: which agent was used, how long it took to respond, whether you accepted or rejected the suggested edits, and how many lines of code were involved. For Zed's own agent, we also capture which underlying model powered the response. We do not collect the content of your prompts, the code you're working on, or any personally identifiable information.
-
What we exclude: To ensure the data reflects real-world usage, we exclude all interactions from Zed staff accounts and from Zed Nightly builds (which may contain experimental or unstable behavior). We also apply minimum thresholds: agents and models with very low usage volumes are not displayed to avoid misleading statistics from small sample sizes.
-
How we calculate metrics: Turn time is measured from request initiation to response completion in milliseconds. Error rate is the percentage of turns that resulted in a failure status.
-
When we update: Data is refreshed every week. This cadence allows newly released models and agents to accumulate enough usage for statistically meaningful comparisons while keeping the data reasonably current.
-
Known limitations: Model-level breakdowns are only available for Zed's own agent. External agents like Claude Agent and Codex don't reliably expose which model they're using in their telemetry. We also cannot detect user subscription tiers (e.g., whether someone is using Gemini's free or paid tier), which may affect performance characteristics.