Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Safeguard and refusal notices now name the category and validate the request ID

You'll notice
Useful3 Signal2
API Errors

Safeguard and refusal notices now end with a Details line naming the refusal category.

What

When the API flags or refuses a message, the notice now ends with a Details: line naming the server-supplied refusal category. This applies to the safeguards notices, their switched-model and same-model variants, and the invalid-request path.

Details
  • The category is stripped of backticks and square brackets and length-capped before being shown; if the response carries no category, or it is not a string, no line is appended.
  • The Request ID appended to refusal messages is now only shown when it matches ^[A-Za-z0-9_-]{1,255}$.
  • The cyber-refusal fallback latch re-arms on a sawCyberRefusal flag as well as on the category, and takes its request id from an entry that is genuinely categorised as cyber.
Evidence

's safeguards flagged this message. , tengu_refusal_fallback_resume_latch

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.234 →