Skip to content

Conversation

@code-yeongyu
Copy link
Owner

@code-yeongyu code-yeongyu commented Dec 11, 2025

OpenAI released GPT-5.2 today with significant improvements:

  • 38% fewer errors in thinking responses
  • Better at coding, planning, and multi-step tasks
  • Improved performance on SWE-Bench Pro and GPQA Diamond

Haha now we got the most brilliant oracle here

OpenAI released GPT-5.2 today with significant improvements:
- 38% fewer errors in thinking responses
- Better at coding, planning, and multi-step tasks
- Improved performance on SWE-Bench Pro and GPQA Diamond
@code-yeongyu
Copy link
Owner Author

Kinda funny that i use cc here but like i made this PR on my iphone with just one prompt

Instead of hardcoding specific GPT versions (5.1, 5.2, etc.),
use regex pattern to support all GPT 5+ models:
- gpt-5, gpt-5.1, gpt-5.2, gpt-6, gpt-10, etc.
- Variants like gpt-5.2-codex -> gpt-5.2-codex-high
- Effort levels like gpt-5.2-medium -> gpt-5.2-high
Add explicit high variant mappings for:
- GPT-5: base, codex, low/medium effort levels
- GPT-5.1: base, codex, codex-max, low/medium effort levels
- GPT-5.2: base, instant, thinking, pro, codex, low/medium effort levels

Also include xhigh variants in ALREADY_HIGH set (new in GPT-5.2 API).
- gpt-5.2 = Thinking (default)
- gpt-5.2-chat-latest = Instant
- gpt-5.2-pro = Pro (supports medium/high/xhigh)
- Added gpt-5-mini
- Removed non-existent instant/thinking/codex variants
Removed fake model IDs with reasoning effort suffixes (-low/-medium/-high/-xhigh).
These are NOT valid model IDs - reasoning effort is passed as a separate parameter.

Valid GPT models:
- GPT-5: gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, gpt-5-chat-latest
- GPT-5.1: gpt-5.1, gpt-5.1-chat-latest, gpt-5.1-codex, gpt-5.1-codex-mini, gpt-5.1-codex-max
- GPT-5.2: gpt-5.2, gpt-5.2-chat-latest, gpt-5.2-pro

The "-high" suffix in HIGH_VARIANT_MAP output is an internal convention
to signal that reasoning_effort should be set to "high" for these models.
@code-yeongyu code-yeongyu merged commit 5072717 into master Dec 11, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants