docs(anthropic): clarify the Opus 4.5 branch in adaptive-effort translation - #32876
Conversation
Greptile SummaryThis PR adds a single inline comment to
Confidence Score: 5/5Pure inline comment addition with zero runtime impact — safe to merge. The change is a single inline code comment that records why a specific branch exists. No executable lines are touched, no tests are modified, and the comment accurately describes the branching logic already in place. No files require special attention.
|
| Filename | Overview |
|---|---|
| litellm/llms/anthropic/experimental_pass_through/messages/transformation.py | Comment-only change: adds an explanatory inline comment above the effort-capable non-adaptive branch in _translate_adaptive_effort_for_non_adaptive_model, clarifying the Opus 4.5 use-case. No runtime behavior changes. |
Reviews (1): Last reviewed commit: "docs(anthropic): clarify the Opus 4.5 br..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…lation Add an inline comment explaining that the effort-capable non-adaptive branch in _translate_adaptive_effort_for_non_adaptive_model exists for models like Claude Opus 4.5 that accept output_config.effort but reject adaptive thinking, and why effort-only requests pass through while adaptive requests with an unsupported effort level fall through to the legacy translation.
0ad512b to
a34f098
Compare
Relevant issues
Linear ticket
Pre-Submission checklist
Screenshots / Proof of Fix
Comment-only change; no runtime behavior changes. Existing tests for the method are unaffected
Type
📖 Documentation
Changes
Follow-up to #32867. Adds an inline comment on the effort-capable non-adaptive branch of
_translate_adaptive_effort_for_non_adaptive_modelexplaining that it exists specifically for models like Claude Opus 4.5 that natively acceptoutput_config.effortbut rejectthinking:{type:adaptive}. The comment records why the adaptive block is dropped while the native effort is kept, and why effort-only requests pass through (so bedrock/vertex subclasses keep owning effort-level clamping) whereas an adaptive request with an unsupported effort level falls through to the legacy budget translationNo behavior change