Usage Data
The cedr command line tool sends anonymous usage data to cedr.dev, so we can see how many people use it, on which systems and with which coding agents, and fix what breaks. It is on by default. The first time cedr would send anything, it says so and tells you how to turn it off.
Turn It Off
Section titled “Turn It Off”Any one of these turns it off:
cedr telemetry off # also deletes your install ID and anything not yet sentexport CEDR_TELEMETRY=0export DO_NOT_TRACK=1cedr telemetry status shows whether it is on and what turned it off; cedr telemetry on turns it back on with a new install ID.
What Is Sent
Section titled “What Is Sent”Each command you run adds one event:
| Field | Example |
|---|---|
| Command | route pick, sync, monitor push: the command’s name from cedr’s own list, never its arguments |
| Exit code | 0 |
| Duration | 41 milliseconds |
| cedr version | 0.5.0 |
| Time | 2026-10-30T18:02:11Z |
| Counts | How many routes, synced agents, pinned skills and servers, or failing doctor checks the command saw |
With each batch of events:
| Field | Example |
|---|---|
| Install ID | A random ID created on your machine, not linked to you, your machine or your cedr.dev account |
| CI | Whether cedr ran in CI. CI runs get a new random ID each time and are counted as runs, not people |
| OS and architecture | linux, x86_64 |
| Coding agents | Which of Claude Code, Codex, Gemini CLI, Copilot CLI, opencode, Muse Code, Antigravity and Cursor have their settings folder on this machine. cedr checks the folder exists; it does not read it |
What Is Never Sent
Section titled “What Is Never Sent”Arguments or flag values, file, folder or repo names, host or user names, error messages, prompts, code, environment variables or API keys. cedr.dev does not store your IP address with the data.
How It Is Sent
Section titled “How It Is Sent”Events wait in a small file on your machine and go to https://api.cedr.dev/v1/telemetry in the background, at most once an hour. Sending never slows a command down or changes what it prints, and nothing is retried after 7 days. We keep individual events for 90 days and daily totals after that.
cedr mcp never shows the notice, because your agent keeps its output; it sends nothing until you have run another cedr command yourself and seen the notice there.