Telemetry in Zed

Zed collects anonymous telemetry to understand usage patterns and diagnose issues.

Telemetry falls into two categories:

Client-side: Usage metrics and crash reports. You can disable these in settings.
Server-side: Collected when using hosted services like AI or Collaboration. Required for these features to function.

Configuring Telemetry Settings

You have full control over what data is sent out by Zed. To enable or disable some or all telemetry types, open Settings ({#kb zed::OpenSettings}) and search for "telemetry", or add the following to your settings file:

json

"telemetry": {
    "diagnostics": false,
    "metrics": false
},

Dataflow

Telemetry is sent from the application to our servers every 5 minutes (or when 50 events accumulate), then routed to the appropriate service. We currently use:

Sentry: Crash-monitoring service - stores diagnostic events
Snowflake: Data warehouse - stores both diagnostic and metric events
Hex: Dashboards and data exploration - accesses data stored in Snowflake
Amplitude: Dashboards and data exploration - accesses data stored in Snowflake

Types of Telemetry

Diagnostics

Crash reports consist of a minidump and debug metadata. Reports are sent on the next launch after a crash, allowing Zed to identify and fix issues without requiring you to file a bug report.

You can inspect what data is sent in the Panic struct in crates/telemetry_events/src/telemetry_events.rs. See also: Debugging Crashes.

Client-Side Metrics

Client-side telemetry includes:

File extensions of opened files
Features and tools used within the editor
Project statistics (e.g., number of files)
Frameworks detected in your projects

This data does not include your code or sensitive project details. Events are sent over HTTPS and rate-limited.

Usage data is tied to a random telemetry ID. If you've authenticated, this ID may be linked to your email so Zed can analyze patterns over time and reach out for feedback.

To audit what Zed has reported, run {#action zed::OpenTelemetryLog} from the command palette or click Help > View Telemetry Log.

For the full list of event types, see the Event enum in telemetry_events.rs.

Server-Side Metrics

When using Zed's hosted services, we collect metadata for rate limiting and billing (e.g., token usage). Zed does not store your prompts or code unless you explicitly share them via feedback ratings.

For details on AI data handling, see Zed AI Features and Privacy.

Concerns and Questions

If you have concerns about telemetry, you can open an issue or email [email protected].