Unclear The finding doesn't identify which operation this outcome list belongs to.
What
An internal list of terminal outcomes for some bounded operation, previously timeout, error, and truncated, now also includes refused and input_too_long.
Why
This lets Claude Code distinguish more specifically between different kinds of failures for this operation, though which operation it applies to isn't specified.
Names in the bundlerefusedinput_too_long
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on handle-streaming-refusals touched a line naming refused after this was published.
Usage metrics are still provided in the response, even when the response is refused. Whether a refused request is billed depends on when the refusal arrives and its category; see [How refusals are billed](https://platform.claude.com/docs/e…test-and-evaluate/strengthen-guardrails/handle-streaming-refusals see the edit
Confirmed since
Anthropic's documentation has since written up refused, on optimizing-for-cost-and-intelligence.
9. **GPQA Diamond:** Rein et al., "GPQA: A Graduate-Level Google-Proof Q\&A Benchmark," 2023. The 198-question Diamond subset, two runs per configuration, run August 7, 2026 (Claude Opus 5.5: September 19, 2026), model-graded against refer…about-claude/models/optimizing-for-cost-and-intelligence see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't identify which operation this outcome list belongs to.
Anthropic's documentation agrees
Anthropic's documentation has since written up refused, on optimizing-for-cost-and-intelligence.