Telemetry

Agent Relay collects anonymous usage data to help us improve the product. This page explains what we collect, why, and how to opt out.

Opt out anytime

Telemetry is on by default but can be disabled instantly:

agent-relay telemetry disable

Or set the environment variable:

export AGENT_RELAY_TELEMETRY_DISABLED=1

Agent Relay also honors the DO_NOT_TRACK convention for opting out across compatible tools:

export DO_NOT_TRACK=1

To re-enable:

agent-relay telemetry enable

Check your current status:

agent-relay telemetry

What we collect

Every event includes these common properties:

Property	Example	Purpose
`agent_relay_version`	3.2.22	Know which versions are in use
`os`	darwin	Platform-specific bug triage
`arch`	arm64	Binary distribution decisions
`node_version`	20.11.0	Runtime compatibility

These events are collected:

Event	When	Extra properties
`broker_start`	Broker process starts	None
`broker_stop`	Broker shuts down	Uptime, agent count
`agent_spawn`	An agent is created	CLI type, spawn source, has task, is shadow
`agent_release`	An agent is stopped	CLI type, reason, lifetime, source
`agent_crash`	An agent exits unexpectedly	CLI type, lifetime, exit code
`message_send`	A relay message is sent	Is broadcast, has thread
`cli_command_run`	A CLI command is executed	Command name

What we do not collect

Source code, file paths, or repository content
Message text, task descriptions, or prompts
API keys, tokens, or credentials
Agent names or workspace names
IP addresses (geo-IP is coarsened to country level by PostHog)
Any personally identifiable information

How it works

A random anonymous ID is generated from your machine ID on first run. It cannot be traced back to you.
Events are sent to PostHog (our analytics provider) over HTTPS.
Preferences are stored locally at ~/.agent-relay/telemetry.json.
The telemetry module is designed to be infallible — if anything fails, it silently no-ops. Telemetry never affects CLI functionality.

Why we collect telemetry

Agent Relay is a developer tool. Telemetry helps us understand which CLI providers are popular, how long agent sessions last, where crashes happen, and which commands are used. This data directly informs what we build and fix next.

Source code

The telemetry implementation is fully open source. You can inspect exactly what is collected: packages/telemetry