Back

langchain #35036

fix(anthropic): support output_config

by ccurme · Feb 06, 2026 at 19:28 UTC · scan-34f78f033c5b361f

View on Github · Download JSON
Medium Risk (30%)

Get this automatically on every PR

Install the Axiomo GitHub App to get Signals as check runs and PR comments on every pull request.

Install App

Risk Assessment

Risk level: Medium (30%)

Risk Drivers

  • deletion_heavy: Removes 122 lines (73% of changes)
  • api_surface_change: API surface changed in 2 file(s)

Intent

2/3 criteria met

Support output_config for response formatting in the Anthropic chat model.

Acceptance Criteria

  • ✓
    Conversion from response_format to output_config occurs correctly.

    chat_models.py changes output_format to output_config.format.

  • ✓
    Tests are updated to ensure output_config is supported.

    Test files modified to remove betas related to structured outputs.

  • ?
    New or modified tests ensure all existing functionality remains intact.

    No additional tests, changes mainly removal in test_chat_models.py.

Confidence: 90.0% Source: diff analysis AI: openai

Contributors

ccurme PR Author 3 commits + Trusted
Account Age: 3245 days
Prior PRs: 1153
Merged: 1100

Trusted contributor with 1100 merged PRs. has 207 followers.

Evidence

Evidence Completeness: 82.0%
ci_passing Passing
security_scan_clean Passing
tests_passing Unavailable
build_successful Passing
lint_passing Passing
Missing: coverage_maintained

Supply Chain

None Risk
Modifies dependencies
Modifies lockfile
Modifies CI config
Modifies build scripts

Focus Files

Review 1 high-priority file(s)

libs/partners/anthropic/tests/unit_tests/test_chat_models.py +108

108 lines changed; Source code

high
libs/partners/anthropic/langchain_anthropic/chat_models.py +57

57 lines changed; Source code

medium
libs/partners/anthropic/tests/integration_tests/test_chat_models.py +2

Source code

medium
libs/partners/anthropic/tests/cassettes/test_response_format_in_agent.yaml.gz +0

Standard file

low
libs/partners/anthropic/tests/cassettes/test_strict_tool_use.yaml.gz +0

Standard file

low

Triage

31

minutes to review

medium

effort level

none

staleness risk

Standard review process

Recommendation

APPROVE 79.0% readiness

Good evidence, acceptable risk, ready for merge

Next Steps

Question

Why is coverage_maintained missing? Consider adding this check.