See and change Claude Code's telemetry settings

Before you start

• ccdeck running, in your browser or the desktop app: npx ccdeck.
• Claude Code on the same machine: Radar reads its settings and watches its connections.

Steps

1. Open Telemetry Radar

   Click the Telemetry Radar icon on the stripe on the right, below Browser Watch’s eye. It has no key. On a phone, it is under More in the dock along the bottom. The dialog is marked Beta.

   

2. Read what Claude Code is set to send

   Click Configuration. Destinations lists where the export goes. Under Telemetry and content, each flag a settings file sets has its name, its variable and the file it came from: Your prompts is OTEL_LOG_USER_PROMPTS, for one.

   

   Settings, not sessions. Radar reads files. A session started before a change keeps what it loaded, and a variable set only in your shell does not show. “No destination found” does not mean telemetry is off.

   More about what Radar reads

   • The env block of three files: ~/.claude/settings.json (under CLAUDE_CONFIG_DIR when that is set), the cached organization settings beside it, remote-settings.json, and the managed settings file, managed-settings.json in /Library/Application Support/ClaudeCode/ on macOS, /etc/claude-code/ on Linux or C:\Program Files\ClaudeCode\ on Windows.
   • Not a project’s .claude/settings.json.
   • A destination shows without its path, and headers as “Configured (hidden)”.
   • All variables and sources lists every variable read, and whether each file was found.
   • With no destination set, Radar lists the connections Claude Code has open. A connection is not telemetry.

3. Switch a flag for new sessions

   Click the switch beside the flag. Radar writes "1" or "0" for it under env in ~/.claude/settings.json and says Saved to user settings. Sessions already running keep the value they started with.

   Radar switches only flags a settings file already sets; it adds none. A flag your organization or managed settings set shows Managed: only an administrator can change it. A value Radar cannot read gets Enable and Disable buttons instead.

   Switching off writes “0”, and it outlasts ccdeck. npx ccdeck --uninstall leaves it in place. To remove it, edit env in the file.

4. Start monitoring your collector

   Click Monitor, pick the destination, then click Start monitoring. ccdeck runs the capture itself: nothing to paste into a terminal. It listens until you click Stop monitoring or ccdeck exits, and starts again when ccdeck next starts on the same port.

   Capture needs a permission once. On macOS, install Wireshark’s ChmodBPF helper. On Linux, give your user capture permission for tcpdump. On Windows, install Wireshark with Npcap, with capture access for your user. ccdeck changes no permission itself.

   More about destinations

   • The list holds your configured destinations that are IPv4 addresses. For a collector set by name, click Another IPv4 address… and type its address and port.
   • It also offers the connections Claude Code has open, marked “telemetry unverified”.
   • Up to eight destinations at once.
   • Closing the dialog or the browser does not stop monitoring.
   • Only whether monitoring is on and its destinations are saved, in ~/.agents-deck/radar-monitor-<port>.json; never packets or messages.

5. Read a message

   Each export Radar decodes is a row: its event or metric name, the session it came from, and whether the collector accepted it. Click a row. Overview shows its fields; JSON, the decoded export.

   Open the full-size picture

   

   What Radar cannot show:

   • Anything but OTLP over gRPC without TLS to an IPv4 address. An HTTPS export shows only as a connection it cannot read.
   • Which program sent it: Radar filters by address, so another app sending there shows too.
   • Claude Code’s requests to the model, and Anthropic’s own telemetry.
   • Proof either way: a connection is not a sent message, and an empty list does not mean telemetry is off.

6. Stop, and clear what was captured

   Click Stop monitoring. What Radar decoded stays in ccdeck’s memory, for 24 hours at most, and is never written to a file or sent anywhere. To remove it now, open Filters and history, click Clear history, then Confirm clear history. Restarting ccdeck removes it too.

If something goes wrong

Something else? See Troubleshoot ccdeck: status, logs, port and hooks.