Repository navigation
fix(anthropic): fail fast on refusal stop_reason instead of retrying as invalid JSON - #5616
Merged
Merged
Conversation
nicoloboschi
force-pushed
the
fix/anthropic-refusal-no-retry
branch
from
October 15, 2026 12:35
3acb650 to
bdd9cbb
Compare
This was referenced Oct 16, 2026
Merged
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.
Fixes #5201.
The native
anthropicprovider gets refusals as HTTP 200 withstop_reasonrefusal/content_filterand an empty body. That empty body was parsed as invalid JSON and retried, so one refused chunk cost 4–16 paid calls, and the worker re-queued it.Now both
callandcall_with_toolsraiseProviderContentPolicyErrorright after the response arrives — same behaviour as #3698 for claude_code: one call, no retry at any layer.Test:
tests/test_anthropic_refusal.py(fails without the fix).