[App] create_thread advertises gpt-5.6-sol/xhigh but rejects it during validation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
Research direction
Start at the codex_app.create_thread tool description and its create-path reasoning-effort validator, then trace how each gets model capabilities. Reproduce the gpt-5.6-sol/xhigh request and verify that the advertised and accepted combinations come from one versioned authority, with the create response identifying the selected model and reasoning effort.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using?
Codex App 26.715.7063.0
What subscription do you have?
Not included in this report.
What platform is your computer?
Windows 11 Pro 10.0.26200 x64
What issue are you seeing?
The first-party codex_app.create_thread tool description on the calling host explicitly advertises this combination:
- model:
gpt-5.6-sol - reasoning effort:
xhigh
However, a single capability-only create attempt with exactly that model/effort pair was rejected before thread creation with:
create_thread could not validate reasoning effort "xhigh" for model "gpt-5.6-sol". Use a model and reasoning combination listed in the tool description, or omit thinking.
This makes the operation-specific capability contract self-contradictory: the exposed tool schema/description says the pair is supported, while the create-path validator says it is not.
The observation was made at 2026-07-19T15:18:09Z. After the rejection, an exact read-only lookup using a unique correlation token found zero created threads. The request was not retried.
What steps can reproduce the bug?
- Start a Codex Desktop thread where the
codex_app.create_threadtool description listsgpt-5.6-solwith supported reasoning efforts includingxhigh. - Invoke
create_threadonce with:- a projectless target
model: "gpt-5.6-sol"thinking: "xhigh"
- Observe that the create-path validator rejects the same combination that the tool contract advertised.
What is the expected behavior?
The advertised contract and the create validator should derive from one versioned capability authority.
Either:
gpt-5.6-sol/xhighis accepted bycreate_thread; orxhighis omitted from the advertisedgpt-5.6-solcreate capability.
On success, the create response should include enough operation-specific evidence to identify the actual selected model and reasoning effort. Ambiguous responses should also be reconcilable without requiring a retry.
Additional information
Only one create attempt was performed. No benchmark, duplicate create, model mutation, or session mutation was run.
- 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 ·