Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

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

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

You'll notice Improvements
JSON All of v2.1.234
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
API ErrorsArea: what it touches
ImprovementsKind: in v2.1.234,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.234 →

Feedback