[BUG] otelHeadersHelper is not being called - No errors or logs indicate issue

Resolved 💬 3 comments Opened Apr 20, 2026 by red8888 Closed Apr 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

otelHeadersHelper is never executed

What Should Happen?

otelHeadersHelper should execute the command

Error Messages/Logs

I can't figure out how to troubleshoot this I'm getting no logs or error messages from claude

My own log file in the script is never created indicating its not being called. I confirmed the command works though.

Steps to Reproduce

Token script:

TOKEN=$(gcloud auth print-identity-token --impersonate-service-account=xxxxx --include-email --audiences=xxxx 2>/dev/null)
HEADER="{\"Authorization\":\"Bearer $TOKEN\"}"
echo "Called" >> "/Users/ME/.claude/otel-debug.log"
echo $HEADER

Settings file:

{
 "env": {
    "CLAUDE_LOG_LEVEL":"debug",
    "CLAUDE_CODE_OTEL_HEADERS_HELPER_DEBOUNCE_MS":"540000",
    "CLAUDE_CODE_USE_VERTEX": "1",
    "CLOUD_ML_REGION":"global",
    "ANTHROPIC_VERTEX_PROJECT_ID":"xxxxxx",
    "DISABLE_PROMPT_CACHING":"1",
    "CLAUDE_CODE_ENABLE_TELEMETRY":"1",
    "OTEL_METRICS_EXPORTER":"otlp",
    "OTEL_LOGS_EXPORTER":"otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL":"grpc",
    "OTEL_EXPORTER_OTLP_ENDPOINT":"xxxxxxx",
    "OTEL_EXPORTER_OTLP_TIMEOUT":"120000",
    "OTEL_METRIC_EXPORT_INTERVAL":"5000",
    "OTEL_LOGS_EXPORT_INTERVAL":"5000",
    "OTEL_RESOURCE_ATTRIBUTES":"department=xxxx,team.id=xxx,cost_center=xxxx"
  },
  "otelHeadersHelper":"bash /tmp/claude_otel_refresh_token.sh"
}

I get not errors and otelHeadersHelper is never executed.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.81 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗