feat: support max reasoning effort - #572
Open
MattSyska wants to merge 1 commit into
Open
Conversation
MattSyska
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What we are solving
Codex supports
maxreasoning effort, but the Claude Code bridge currently rejects--effort maxbefore it reaches Codex. Users therefore cannot select the highest supported effort through/codex:rescue.Why
Max is useful for difficult bounded work and lets orchestrators exhaust a cheaper execution model's reasoning range before escalating to a more expensive model.
Changes
maxin the companion bridge validator and CLI help.maxin the rescue command and runtime skill.Testing
npm test— 91 tests passedgit diff --check