Skip to main content
Two optional integrations you can toggle from the CLI: anonymous product telemetry, and the Claude Code statusline. Both map to config keys, and these commands are the convenient way to flip them.

Telemetry

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 has no effect on your own analytics.
ironbee telemetry disable   # opt out
ironbee telemetry enable    # opt back in (the default)
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.
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.

Statusline

Statusline integration is Claude Code only.
IronBee can surface session status in Claude Code’s statusline while preserving any statusline you already have:
ironbee claude statusline enable    # install the statusline wrapper
ironbee claude statusline disable   # restore your original statusline
enable installs a wrapper that emits session_status events and chains your existing statusline; disable restores it and stops emitting. Same layer flags as telemetry (-g, --local). If you change your upstream statusline mid-session, re-resolve the chained wrapper for active sessions:
ironbee claude statusline sync
For statusline behavior options (rendering a default line, emit throttling, refresh interval), see the statusLine.* keys in Configuration.

What’s next?

Configuration

The telemetry.* and statusLine.* keys in full.

Privacy Mode

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