Feature request: Keep model-control terminology in English across all UI locales

Open
#34,646 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos

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

app enhancement
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:

  • Model
  • Effort
  • Speed
  • Light, Medium, High, Extra High, Max, and Ultra
  • 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

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.