Feature request: Keep model-control terminology in English across all UI locales
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- macos
- Domain
- desktop, internationalization
Research direction
No files, tests, or implementation entry points are named; start by locating the model-control labels, tier values, and locale resources used by Codex Desktop. Done means those model-control terms and model names remain in English in every supported locale while surrounding UI text continues to follow the selected language.
Written by the indexing model from the issue text.
Description
What variant of Codex are you using?
Codex Desktop app on macOS
What feature would you like to see?
Keep model-control terminology in English across all UI locales
The built-in model controls should use one stable English vocabulary regardless of the application's display language. This should apply equally when the rest of the app is in Chinese, Russian, Spanish, Korean, Japanese, or any other supported locale.
Scope: invariant English terminology
The following technical labels and values should remain English wherever the built-in model controls appear:
ModelEffortSpeedLight,Medium,High,Extra High,Max, andUltra- model-family and model-variant names
This should be a product-wide terminology contract, not a special exception or per-user setting for one locale.
Locale behavior outside that vocabulary
The surrounding application UI should continue to follow the selected UI language. In particular, generic navigation, actions, accessibility labels, and explanatory/help copy can remain localized.
For example, an action such as “Reset to default” and a usage explanation can follow the UI locale, while the model-control terms and tier names remain English.
Current behavior
The app language setting localizes the model-control vocabulary together with the rest of the application. That creates different translations for technical concepts that are commonly referenced in English in documentation, release notes, API terminology, support material, and cross-language team discussions.
Requested behavior
Treat the model-selection vocabulary as fixed English product terminology in every locale, while retaining localization for the rest of the app.
This would provide:
- consistent terminology across platforms and locales;
- an exact match between in-app controls and English technical documentation;
- easier collaboration and support across multilingual teams; and
- less ambiguity caused by locale-specific translations of model and reasoning concepts.
Related issue
This is intentionally distinct from #27255. That issue requests complete Chinese localization for general UI strings. This request asks that a narrow set of model-control terms be intentionally excluded from that localization so the technical vocabulary stays consistent globally.
Environment
- Codex Desktop for macOS
- App version:
26.715.70719 - This request applies to all UI locales
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·