envden v0.1.0 is in alpha
Skip to Content
.envden

Control telemetry

Choose whether the CLI sends usage events and see what they contain.

Turn telemetry on or off

Telemetry is off by default. Interactive setup asks whether you want to enable it. Setup with --yes or without a terminal leaves it off unless you explicitly choose --telemetry on.

Change the preference at any time:

envden config telemetry on
envden config telemetry off

ENVDEN_TELEMETRY=0 and DO_NOT_TRACK=1 override the saved preference and disable events.

Read the saved preference:

envden config telemetry

This prints true or false. Run envden config to see the saved settings and effective telemetry and update-check preferences.

What an event contains

Events include the envden version, OS, command name, success or failure, a fixed error code, counts and a random install ID.

They exclude raw errors, stack traces, Repo IDs, file names, key names, values, server addresses and network identity. The shell notice and server send no telemetry.

Where events go

The CLI sends events to PostHog using fetch. The PostHog project is configured to discard IP addresses and skip GeoIP, but PostHog still sees the connection's IP address.

The daily update check is separate. It fetches a signed release feed from GitHub Releases and has its own setting.

On this page