AgentDX collects anonymous, aggregate telemetry to understand which agents and features are used most. This helps prioritize development and catch integration issues early.

Telemetry is entirely optional. You can disable it before AgentDX ever sends a single ping.


What We Collect

Each telemetry payload contains the following fields:

Field Example Purpose
v 1 Payload schema version
ts 1717200000000 Unix timestamp (ms) of the ping
install_id a3f8c1... (32-char SHA-256 hash) Random, non-reversible installation identifier
period 2025-06-01 Date the stats cover
agents { "claude-code": { sessions: 12, tokens: 50000, ... } } Per-agent aggregate counts
models { "claude-opus-4-6": { calls: 80, ... } } Per-model aggregate token counts
tools_top10 ["Read", "Edit", "Bash", ...] Top 10 tool names by call count (names only, no content)
languages ["typescript", "python"] Programming languages detected in repositories
session_count 42 Total number of sessions in the database
avg_duration_ms 185000 Average session duration
os darwin Operating system
arch arm64 CPU architecture

The payload is sent as a single HTTPS POST to https://t.agentdx.ai/v1/ping with a 5-second timeout. If the request fails, it is silently dropped -- telemetry never blocks or retries.


What We NEVER Collect

The install_id is a one-way SHA-256 hash of a random value. It cannot be reversed to identify you or your machine.


How to Opt Out

CLI

npx agentdx telemetry off

Environment Variable

export AGENTDX_TELEMETRY=off

Set this in your shell profile (.bashrc, .zshrc, etc.) to disable telemetry permanently.

Config File

Edit ~/.agentdx/config.json:

{
  "telemetry": false
}

Any of these methods takes effect immediately. No restart required.

Verify Status

npx agentdx telemetry

This prints whether telemetry is enabled or disabled and shows exactly what would be sent.


Data Retention


Contact

Questions or concerns about data privacy: