[FEATURE] OTLP telemetry export not supported in JetBrains and VSCode IDE plugins

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The CLI and Cowork both support custom OTLP telemetry export via OTEL_* environment variables and managed settings. However, the JetBrains and VSCode plugins do not pick up these settings, making it impossible to monitor IDE plugin usage alongside CLI/Cowork usage in a centralised OTel dashboard. For Teams/Enterprise customers tracking usage across an organisation, this creates a blind spot for IDE users.

Proposed Solution

Proposed solution: The IDE plugins should inherit the same OTLP telemetry configuration as the CLI. Specifically:

1. Read the env block from managed settings (remote-settings.json) and pass OTEL_* environment variables to the underlying Claude Code subprocess
2. Alternatively, have the IDE plugins read OTEL_* variables from the system environment when launching the Claude Code process

Since the plugins already run claude as a subprocess, the simplest implementation would be to ensure that subprocess inherits the managed settings environment variables — the same way the standalone CLI
already does. No new telemetry code would be needed in the plugins themselves.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_