Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop App / codex app-server does not honor project-scoped OTel config in trusted projects [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17110•Fetched 2026-04-09 08:02:15
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
FMnagaFMnaga
Participants
FMnagaFMnagagithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1unlabeled ×1

Root Cause

This makes team-wide telemetry difficult in fork-based rollout because global config is a per-user workaround, not a scalable repository-distributed configuration model.

Fix Action

Fix / Workaround

This makes team-wide telemetry difficult in fork-based rollout because global config is a per-user workaround, not a scalable repository-distributed configuration model.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Codex 26.325.31654 (0.118.0-alpha.2)

What subscription do you have?

ChatGPT Enterprise

What platform is your computer?

Darwin 24.2.0 arm64 arm

What issue are you seeing?

We observed a difference between Codex CLI and Codex Desktop App regarding OpenTelemetry configuration.

  • Codex CLI can read [otel] settings from a trusted project's .codex/config.toml and successfully send OTel logs.
  • Codex Desktop App (appears to run via codex app-server) does not seem to honor the same project-scoped .codex/config.toml OTel settings.
  • If the same [otel] configuration is added to the user's global ~/.codex/config.toml, Codex Desktop App can send telemetry.

This makes team-wide telemetry difficult in fork-based rollout because global config is a per-user workaround, not a scalable repository-distributed configuration model.

What steps can reproduce the bug?

  1. Create a trusted project with .codex/config.toml containing a valid [otel] configuration.
  2. Confirm that codex exec or Codex CLI reads the project-scoped config and exports OTel logs.
  3. Open the same trusted project in Codex Desktop App.
  4. Use Codex Desktop App normally and check whether OTel logs are exported.
  5. Add the same [otel] settings to the user's global ~/.codex/config.toml.
  6. Restart Codex Desktop App and repeat the same test.

Observed result:

  • CLI: project-scoped OTel works
  • Desktop App / app-server: project-scoped OTel appears not to work
  • Desktop App / app-server: global OTel works

Uploaded thread: 019d6bed-eb78-7cc0-bc0f-6c655af763b7

What is the expected behavior?

Codex Desktop App / codex app-server should either:

  1. honor [otel] settings from a trusted project's .codex/config.toml, consistent with Codex CLI, or
  2. explicitly document that OTel is supported only from global ~/.codex/config.toml.

For team usage, project-scoped telemetry should be officially supported because depending on per-user global config does not scale in fork-based rollout.

Additional information

Please clarify whether this is expected behavior or a bug.

The main product request is:

  • document the current intended scope for OTel config (global only vs project-local), and
  • support project-scoped telemetry in Codex Desktop App / codex app-server for organizational rollout.

Feedback thread ID: 019d6bed-eb78-7cc0-bc0f-6c655af763b7

CodexDesktop App: 26.325.31654 Internal Codex binary version: 0.118.0-alpha.2

extent analysis

TL;DR

The Codex Desktop App may not be configured to read OpenTelemetry settings from a project's .codex/config.toml file, unlike the Codex CLI.

Guidance

  • Verify that the .codex/config.toml file is correctly formatted and contains the expected [otel] configuration settings.
  • Check the Codex Desktop App documentation to see if it explicitly states that OpenTelemetry settings are only supported from the global ~/.codex/config.toml file.
  • Test whether the issue persists when using a different project or configuration to isolate the problem.
  • Consider submitting a feature request to support project-scoped telemetry in the Codex Desktop App for better scalability in team environments.

Notes

The current behavior may be intended, but it is unclear without further documentation or clarification from the Codex team.

Recommendation

Apply workaround: Use the global ~/.codex/config.toml file for OpenTelemetry settings until project-scoped telemetry is officially supported in the Codex Desktop App.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING