openai / openai/codex

Settings search returns hidden "Default terminal location" and navigation differs by locale

Open
#46,809 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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

Powered by Codex & OWL, version 26.915.31945, released on 2026-09-18.

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 x64

What issue are you seeing?

The Settings search includes Default terminal location even when that setting is currently hidden because Bottom panel is disabled.

The behavior then differs by app language:

  • Bottom panel OFF + English UI

    • Search for terminal.
    • Click Default terminal location.
    • The settings pane scrolls to the location where the setting would appear, but the target setting itself is not rendered because Bottom panel is disabled.
  • Bottom panel OFF + Chinese UI

    • Search for 终端.
    • Click 默认终端位置.
    • The settings pane does not scroll to the target location at all.
  • Bottom panel ON

    • The Default terminal location setting becomes visible.
    • Search-result navigation works correctly in both English and Chinese.

This suggests two related issues:

  1. Settings search returns a setting that is unavailable/hidden under the current configuration.
  2. When the hidden setting is selected, navigation behavior is inconsistent between English and Chinese locales.
What steps can reproduce the bug?
Case 1: English UI, Bottom panel OFF
  1. Open the Codex/ChatGPT desktop app on Windows.
  2. Set the app language to English.
  3. Open Settings → General.
  4. Make sure Bottom panel is disabled.
  5. Search for terminal.
  6. Click Default terminal location.
  7. Observe that the pane scrolls to the expected area, but Default terminal location is not visible because it is conditionally hidden.
Case 2: Chinese UI, Bottom panel OFF
  1. Set the app language to Chinese.
  2. Keep Bottom panel disabled.
  3. Search for 终端.
  4. Click 默认终端位置.
  5. Observe that the pane does not scroll to the target location.
Control case: Bottom panel ON
  1. Enable Bottom panel.
  2. Search for the same setting in either English or Chinese.
  3. Click the search result.
  4. Observe that navigation works correctly and the setting is visible.
What is the expected behavior?

A settings search result should not lead to a hidden/unavailable control without explanation.

Possible expected behaviors:

  • Hide Default terminal location from search results while Bottom panel is disabled; or
  • Keep it searchable, but reveal/enable the prerequisite or otherwise explain why the setting is unavailable.

If the result remains searchable while hidden, clicking it should behave consistently across locales.

Additional information
  • The setting appears to be conditionally rendered based on Bottom panel.
  • English currently scrolls to the hidden setting's position.
  • Chinese currently does not scroll when the setting is hidden.
  • Once Bottom panel is enabled, both languages work correctly.

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 by reproducing the Settings → General search flow on Windows with Bottom panel disabled in English and Chinese, then compare it with the enabled control case. The payload names no source files or tests, so locate the settings-search and conditional-rendering entry points first. Done means hidden settings are handled consistently, with navigation behaving the same across both locales.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop-dev, localization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.