-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(cli): reject unsupported caps and report ignored legacy values #4043
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Document the separate injection-effort contract.
src/cli/effort.tsacceptsnoneandminimalforocx effort set --injection, but these sections only describe their rejection as cap values. Add an explicit--injectionexample and state that its accepted values are separate from cap validation. Also state that a valid CLI cap can still be mapped or clamped later by a provider adapter.docs-site/src/content/docs/reference/cli/agents.md#L38-L41: document--injection none|minimalseparately from--mainand--subagent, and identify later adapter mapping as a separate layer.docs-site/src/content/docs/ko/reference/cli/agents.md#L21-L24: add the equivalent Korean clarification so it remains synchronized with the English source.As per coding guidelines: “Document current shipped or intentionally pending behavior.” As per path instructions: “Check that user-facing docs stay in sync with actual CLI/API behavior.”
📍 Affects 2 files
docs-site/src/content/docs/reference/cli/agents.md#L38-L41(this comment)docs-site/src/content/docs/ko/reference/cli/agents.md#L21-L24🤖 Prompt for AI Agents
Sources: Coding guidelines, Path instructions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coderabbitai Please reassess this as a scope/documentation suggestion rather than a correctness defect in the changed cap section.
The current paragraph explicitly discusses main/subagent cap values, says
noneandminimalare not cap levels, and separately identifies the retained injection-effort setting. It does not say those values are rejected by every effort option.The proposed unqualified
--injection none|minimalexample would not match the live path. The CLI preserves its separate injection validator, but the existing live injection API accepts onlyisCodexReasoningEffortand returns 400 for those sentinels. They are accepted by the offline CLI path, not consistently by both paths. This pre-existing discrepancy is explicitly preserved and listed as outside this cap correction in the PR description; the new docs avoid promising unsupported live behavior.Provider-specific mapping and cap eligibility are likewise unchanged; the section links the broader subagent guide rather than adding a new mapping guarantee. The change here is canonical cap validation and truthful read-only reporting of ignored legacy values. The complete exact-head contributor CI has now passed all 26 jobs.
No code/doc change is proposed for this comment because the current cap-specific wording is accurate, while the requested general sentinel example would need the separate live/offline policy caveat. Please withdraw/resolve the correctness finding, or identify a specific incorrect claim in the current cap text.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Post
@coderabbitai resolveor@coderabbitai approveas a new top-level PR comment. Approve commands are disabled for review-thread replies.