openai / openai/codex

[Windows][Voice Chat] Starting voice silently resets GPT-5.6 Sol High to Low

Open
#41,727 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug config session windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex are you using?

Codex Desktop on Windows. The bundled runtime recorded in session metadata is codex-cli 0.151.0-alpha.7.2.

What issue are you seeing?

The user-level default is explicitly configured as:

model = "gpt-5.6-sol"
model_reasoning_effort = "high"

Starting Realtime Voice silently creates or updates the voice task with gpt-5.6-sol at low reasoning effort. The user then has to manually switch it back to High every time.

This is not a display-only issue: local session events record thread_settings_applied with reasoning_effort: "low" immediately after voice starts. The configuration file remains unchanged at High.

Steps to reproduce
  1. In Codex Desktop on Windows, select GPT-5.6 Sol with High reasoning.
  2. Confirm the user-level configuration also uses GPT-5.6 Sol and High reasoning.
  3. Start a new Realtime Voice chat.
  4. Inspect the model/reasoning selector or the resulting thread_settings_applied session event.
  5. Observe that the voice task starts as GPT-5.6 Sol with Low reasoning.
  6. Manually change it back to High.
  7. Start another voice chat and observe the same reset.
Expected behavior

Realtime Voice should preserve the user's selected/default model and reasoning effort. If the product needs a lower-latency internal voice model, that internal choice should not overwrite the Codex task's selected model or reasoning level.

Actual behavior

Voice startup silently overrides High with Low.

Reproduction evidence

This reproduced in three separate voice sessions on the same day:

Voice session First applied setting User-restored setting
1 GPT-5.6 Sol / Low GPT-5.6 Sol / High
2 GPT-5.6 Sol / Low GPT-5.6 Sol / High
3 GPT-5.6 Sol / Low GPT-5.6 Sol / High

In one longer-running session, the setting later changed from High back to Low again and then had to be restored manually.

No session IDs, local paths, account details, or private logs are included here. The exact event timestamps and redacted session evidence can be provided privately if maintainers need them.

Related

This appears related to voice-task configuration inheritance problems reported in #39269, but this reproduction is narrower: even a valid persistent default of GPT-5.6 Sol / High is overridden to Low whenever voice starts.

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.

Research direction

Start with Realtime Voice startup and the thread_settings_applied event, then trace how the selected model and reasoning effort are inherited when a voice task is created. Compare the persistent High setting with the Low value applied after voice starts; done means voice preserves the user's selected model and reasoning effort without changing the configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
audio-video-rtc, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.