> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ironbee.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Telemetry & Statusline

> Manage anonymous CLI telemetry and the Claude Code statusline integration.

Two optional integrations you can toggle from the CLI: anonymous product telemetry, and the Claude Code statusline. Both map to [config keys](/cli/configuration/configuration), 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.

```bash theme={null}
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`](/cli/configuration/configuration#telemetry).

<Note>
  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](/cli/advanced/privacy).
</Note>

***

## Statusline

<Note>
  Statusline integration is **Claude Code only**.
</Note>

IronBee can surface session status in Claude Code's statusline while preserving any statusline you already have:

```bash theme={null}
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:

```bash theme={null}
ironbee claude statusline sync
```

For statusline behavior options (rendering a default line, emit throttling, refresh interval), see the [`statusLine.*` keys](/cli/configuration/configuration#statusline-claude-code-only) in Configuration.

***

## What's next?

<CardGroup cols={2}>
  <Card title="Configuration" icon="settings" href="/cli/configuration/configuration">
    The `telemetry.*` and `statusLine.*` keys in full.
  </Card>

  <Card title="Privacy Mode" icon="bot" href="/cli/advanced/privacy">
    Redact tool detail, screenshots, and recordings from the data the DevTools MCP servers ship to the Collector.
  </Card>
</CardGroup>
