Desktop app agent sessions don't apply OTel telemetry env from managed settings

Summary

Org-wide managed settings configure Claude Code telemetry (env block with CLAUDE_CODE_ENABLE_TELEMETRY=1, OTEL_LOGS_EXPORTER=otlp, OTEL_METRICS_EXPORTER=otlp, OTEL_EXPORTER_OTLP_PROTOCOL=http/json, OTEL_EXPORTER_OTLP_ENDPOINT=...). CLI and VS Code extension sessions on the same machine export correctly. Claude Desktop app agent sessions do not.

Repro

1. Deliver the telemetry env block via managed settings (observed with both claude.ai admin-console server-managed settings and the local managed-settings.json).
2. Start a CLI or VS Code session → OTLP events arrive at the collector. ✅
3. Start a Desktop-app agent session (fully quit + reopened after config) and inspect its process env: CLAUDE_CODE_ENABLE_TELEMETRY=1 is present, but none of the OTEL_* variables are — so nothing is exported. ❌

Expected

Desktop agent sessions apply the same managed/user settings env block (at least the OTel exporter vars) so org usage dashboards can observe them, like CLI/IDE/SDK entrypoints do.

Notes

The monitoring docs (code.claude.com/docs/en/monitoring-usage) list only CLI/SDK/IDE entrypoints, so this may be by design today — filing as a feature request if so. For orgs measuring adoption with self-hosted OTel receivers, Desktop is currently a blind spot.

Environment: macOS (Darwin 24.6), Claude Desktop app with local agent sessions, telemetry verified working from iTerm/Apple_Terminal/intellij/pycharm/vscode entrypoints on the same machines.