Skip to main content
IronBee collects anonymous usage telemetry (via PostHog) to improve the CLI. This is separate from the IronBee Collector pipeline that ships your session data — turning telemetry off doesn’t change what your Console shows.

​
Enable or disable

Disabling turns telemetry off in both the CLI and the IronBee DevTools MCP servers (it injects TELEMETRY_ENABLE=false into their environment), so one switch covers both sides. By default these write to the project config. Use -g/--global for all your projects or --local for a gitignored personal override. The underlying key is telemetry.enable. For a single shell or CI run, IRONBEE_TELEMETRY=false does the same thing without touching any config file — see Environment variables.
Telemetry is about the CLI’s own anonymous product analytics. To control how much of your session detail (tool input/output, screenshots, recordings) reaches the Collector, see Privacy mode.

​
How it relates to the other data switches

​
What’s next?

Configuration

The telemetry.enable key in full.

Privacy Mode

Redact tool detail, screenshots, and recordings from the data the DevTools MCP servers ship to the Collector.