OpenTelemetry export (OTLP)

Speedwave supports exporting OpenTelemetry (OTLP) metrics and trace logs from Claude Code sessions directly to your enterprise collector. Telemetry is disabled by default. To configure export parameters, navigate to Settings → Telemetry (enable the Beta features toggle in the tray menu to access this panel). Enterprise MDM enforcement applies automatically regardless of user beta flags.

Collector configuration

1. Open Settings → Telemetry and enable the master toggle.
2. Enter the Collector endpoint (e.g. https://collector.example.com:4318).
3. Click Test connection to verify network reachability from the host workstation.
4. Select the transport Protocol: gRPC, http/protobuf, or http/json.
5. Toggle Metrics and Logs export streams according to your monitoring requirements.
6. Provide optional Authentication headers (such as Authorization=Bearer <token>). Once saved, secret values are write-only and masked in the UI.
7. Configure optional Resource attributes and enable Include account UUID to tag metric streams with unique installation identifiers.

Export frequencies are governed by Metric interval and Logs interval values (specified in milliseconds).

Privacy controls for exported logs

Standard metric and event streams export operation counts and durations without capturing conversation text. Four discrete privacy toggles control whether message payloads are included in exported logs (disabled by default):

Privacy control	Telemetry payload
Log user prompts	Raw prompt text submitted to Claude
Log assistant responses	Generated assistant response content
Log tool details	Shell commands, file paths, and tool arguments
Log raw API bodies	Full JSON request and response payloads sent to the LLM provider

Enabling any content toggle requires explicit user confirmation. Content filtering applies exclusively to the log export stream (requiring Export Logs to be active).

Data egress warning

Enabling content logging streams prompt and response text to your external collector endpoint. Verify that destination telemetry endpoints comply with organizational data governance requirements before enabling content logging.

Organization enforcement (MDM)

System administrators can lock telemetry configurations globally by deploying a signed managed-config.json specification to system-level directories:

• macOS: /Library/Application Support/Speedwave/managed-config.json
• Windows: <ProgramData>\Speedwave\managed-config.json (resolved via native Windows Known Folder APIs to prevent environment variable spoofing).

Any key defined within managed-config.json is rendered read-only in the desktop interface, accompanied by an enterprise lock badge. Missing policy files default control to the local user. Malformed configurations or unresolvable policies halt startup with an explicit diagnostic error, preventing fallback to insecure defaults. Setting enabled: false globally disables all telemetry options across the workstation.

Anthropic Console policy isolation

Telemetry policies configured in Anthropic Admin Console do not affect Speedwave sessions. Because Claude Code routes requests through the local Speedwave proxy, upstream console policies are superseded by local managed-config.json settings.

Speedwave enforces managed values at the container process level: user-defined shell environment variables matching managed keys are stripped and replaced with administrative defaults prior to container startup.

For related settings, review Configuration keys, Environment variables, and Data and privacy.