✨ Add 'xhigh' effort level and default to it (refs #81) - #82
Merged
Conversation
Adds XHIGH = "xhigh" to VALID_EFFORT_LEVELS between HIGH and MAX and changes DEFAULT_EFFORT_LEVEL to XHIGH, matching Anthropic's recommended starting point for coding/agentic work on Opus 4.7. Refs #81
5 tasks
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
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.
Summary
XHIGH = "xhigh"toVALID_EFFORT_LEVELSbetweenHIGHandMAX(Opus 4.7-only effort tier from Anthropic's effort docs).DEFAULT_EFFORT_LEVELfromMAXtoXHIGHto match Anthropic's recommended starting point for coding/agentic work on Opus 4.7.0.2.5(pyproject.toml + uv.lock).Refs #81
Notes
askcc/cli.pyuseschoices=VALID_EFFORT_LEVELSand the help string renderssettings.ASKCC_CLAUDE_EFFORT_LEVELdynamically, so--effort xhighand the new default surface automatically._resolve_effort_level()iterates the enum for its warning message — no code change there, but I confirmedASKCC_CLAUDE_EFFORT_LEVEL=xhighno longer triggers the invalid-value warning.Test plan
uv run poe check(ruff) — passesuv run poe typecheck(pyright) — 0 errorsuv run poe test— 155 passed (incl. 2 new tests:test_xhigh_effort_level_resolves_without_warning,test_default_effort_level_is_xhigh)low/high/max/invalid values still pass unchanged