feat: configure Codex telemetry and Claude traces

[tgmendes]

Summary

• configure downloaded Codex install scripts to send native OpenTelemetry logs, traces, and metrics to Gram with a generated hooks key
• enable Claude Code enhanced telemetry and OTLP trace export in managed setup settings
• use OTLP HTTP/protobuf for both clients, matching Gram's generic ingestion decoder
• preserve existing Codex exporters per signal and cover generated TOML plus the authenticated download path

Motivation

The observability plugins already capture hook events, but Codex's quick installer does not configure its native OpenTelemetry exporters and Claude tracing remains disabled. This routes native Codex and Claude OTLP signals through Gram's generic telemetry ingestion path.

Why the endpoint is /otel

OTLP exporters treat the configured value as a base URL and append /v1/logs, /v1/metrics, or /v1/traces. Configuring https://app.getgram.ai/otel therefore targets Gram's generic /otel/v1/* ingestion routes.

The previous https://app.getgram.ai/rpc/hooks.otel base was not provider-neutral: /rpc/hooks.otel/v1/traces is owned by the legacy LiteLLM trace handler. That handler stamps accepted spans with hook_source = "litellm", the litellm:otel:traces resource URN, and LiteLLM tool metadata regardless of the producer's incoming service.name. Claude traffic sent there could therefore appear as LiteLLM even though it never traversed a LiteLLM proxy.

The generic /otel/v1/traces path preserves the producer's OTLP resource attributes, and downstream source attribution derives from service.name, allowing Claude Code telemetry to remain attributed to Claude Code. Claude is configured with http/protobuf and Codex with binary, so their payloads match these routes' protobuf decoder.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fdad285

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cubic-dev-ai]

Running ultrareview automatically — This PR rewrites the Codex install script generator to embed OTLP telemetry and API keys into users' config.toml, adds new API-key persistence, and changes Claude managed settings—any subtle bug could corrupt user configs or break installs, so a deep review is warranted.. I'll post findings when complete.

[tgmendes]

Demo

What it shows:

1. The managed settings flow now calls out logs, metrics, and traces.
2. The generated JSON enables enhanced telemetry and sets OTEL_TRACES_EXPORTER to otlp.

[cubic-dev-ai]

Ultrareview completed in 15m 45s

All reported issues were addressed across 7 files

_{Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.}

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

_{Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.}

<sub>Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 7 files (changes from recent commits).

_{Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.}

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>