ChatGPT Desktop: Work/Codex voice UI is missing in API key authentication mode while Chat voice remains available

Open
#35,498 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos
Domain
authentication, desktop

Research direction

Start by reproducing the behavior on macOS with codex login --with-api-key, then compare voice availability in the Chat, Work, and Codex views while checking the reported RemoteFeatureFlags and logs. Done means establishing whether API-key authentication is expected to omit Work/Codex voice and documenting or resolving the discrepancy.

Written by the indexing model from the issue text.

Description

app auth bug

Summary

When ChatGPT Desktop is authenticated using an OpenAI API key (via codex login --with-api-key), Chat voice remains available, but the Work and Codex views do not display any voice input button.

Environment

  • macOS
  • ChatGPT Desktop 1.2026.184
  • Apple Silicon
  • Authenticated using API key

Expected

Voice should either be available consistently across Chat, Work and Codex, or the UI should indicate that API-key authentication does not support Work/Codex voice.

Actual

  • Chat: Voice button visible
  • Work: No voice button
  • Codex: No voice button

Diagnostics

  • voiceAvailable = 1 in RemoteFeatureFlags.
  • No local preference disabling voice found.
  • com.openai.codex contains only UI/update preferences.
  • Logs contain backend responses including 403 /celsius/ws/user and 500 /wham/tasks/list.
  • Chat voice continues to work normally.
  • ChatGPT Desktop and Codex CLI appear to share authentication state after codex login --with-api-key.

Question: Is this expected behavior for API-key authentication, or a bug/regression?

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.