[codex] Enforce OpenAI reasoning compliance#30
Conversation
Show 1 previous deployments
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (16)
✨ 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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f2daba649b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| appendOption(select, noneValue, noneLabel); | ||
| optionValues.push(noneValue); |
There was a problem hiding this comment.
Hide None when the model does not support it
For models whose stored supported_reasoning_levels do not include none (for example existing/pre-gpt-5.1 Codex snapshots with only low, medium, high, xhigh), this unconditionally advertises a None choice even though the updated backend validation in src/openai.ts rejects explicit none unless it is listed. Selecting it in chat sends reasoning_effort: "none", and selecting it in admin defaults saves the same value, so users are led into a 400 instead of seeing only supported efforts plus Default.
Useful? React with 👍 / 👎.
Summary
Validation