Skip to content

Comments

fix: use raw model names from models/list in model picker fix #430#499

Merged
Dimillian merged 1 commit intomainfrom
codex/github-mention-the-model-gpt-5.3-codex-does-not-exist-or-yo
Feb 23, 2026
Merged

fix: use raw model names from models/list in model picker fix #430#499
Dimillian merged 1 commit intomainfrom
codex/github-mention-the-model-gpt-5.3-codex-does-not-exist-or-yo

Conversation

@Dimillian
Copy link
Owner

Motivation

  • Align the UI with backend-provided model names so displayed labels match the raw values returned by models/list instead of a local title-casing/slug formatter.
  • Users observed a mismatch (e.g. gpt-5.3-codex vs GPT-5.3-Codex) that could be misleading or cause inconsistencies across clients.

Description

  • Stop transforming model slugs for display and instead use the server-provided displayName/display_name when present and non-empty, otherwise fall back to the raw model slug in parseModelListResponse in src/features/models/utils/modelListResponse.ts.
  • Removed the previous slug-formatting usage from the model-list parsing flow.
  • Updated unit tests in src/features/models/utils/modelListResponse.test.ts to assert the new behavior (preserve explicit displayName and use raw slugs when displayName is missing or empty).

Testing

  • Ran the focused unit tests with npm run test -- src/features/models/utils/modelListResponse.test.ts and they all passed.
  • Ran type checking with npm run typecheck and it completed successfully.

Codex Task

@Dimillian Dimillian changed the title Use raw model names from models/list in model picker fix: use raw model names from models/list in model picker fix #430 Feb 23, 2026
@Dimillian Dimillian merged commit b131fc3 into main Feb 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant