Conversation
Codex 0.160 rejects turn/start when settings.model is null.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe Codex turn parameter builder now trims the model value and omits ChangesCodex turn parameters
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: 🔵 Low · up to A model-less planning side answer may lack the Plan instruction preset, though edits remain blocked. This is a bounded behavior issue that can be accepted or addressed separately. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
turn/startno longer sendscollaborationModewhen no model has been selected. A selected model still sends the same mode, effort, and built-in instructions as before. A plan turn with no model still uses the read-only sandbox andapprovalPolicy: "never".Why
Codex 0.160 rejects the turn before it starts:
Invalid request: invalid type: null, expected a stringcollaborationMode.settings.modelis a required string. Sendingnullis that error. Omitting the field ismissing field model. Reproduced againstcodex app-server0.160.0: a thread starts and Codex chooses the model, thenturn/startwithsettings.model: nullfails immediately. The same request with the model omitted fromcollaborationMode, or withsettings.modelset to a real model id, is accepted.reasoning_effort: nullanddeveloper_instructions: nullare fine oncemodelis a string.UI
No layout changes. A Codex turn that previously failed with no reply now starts.
Validation
npm test— 4261 passed, 13 skippednpx tsc --noEmitnpm run test:hostandnpm run host:packageon Node 24.21.0 (the host job's Node version). Node 20 cannot loadnode:sqlite, which the host job does not use.cargo fmt --checkcargo clippy --workspace --all-targets -- -D warningscargo checkcargo test— 539 passed, 1 ignoredChecklist
npm run check(web and Rust steps, matching CI)Made with Cursor
Summary by CodeRabbit