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
HomeReleasesv2.1.223entry #36

Claude Code v2.1.223 ·

Feedback drafts gained failure-mode and task-category fields

Feedback now lets you tag a failure mode and task category, cycled with the arrow keys.

Use it now Improvements
JSON All of v2.1.223
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
FeedbackArea: what it touches
ImprovementsKind: in v2.1.223,
What probably matters to youSection of the release
What

SendFeedback drafts, the review UI, the rendered feedback body and two telemetry events all gained failure_mode and task_category classification.

Details
  • failure_mode is a closed list of 16 model-behaviour issues including instruction_following, destructive_actions, repetition_and_looping, overconfidence_and_hallucination, stopping_short, overeager, subagent_overspawn, tone_or_preachiness and other
  • task_category is one of code_edit, debug, explain, plan, shell, search, review, other
  • both are optional; left and right arrow keys cycle them in the review screen
  • the tool prompt instructs the model to set failure_mode only for model-behaviour reports and omit it for pure product bugs
  • tengu_feedback_draft_submitted now reports both fields
Evidence

When the report is about MODEL BEHAVIOR (not a product bug), the closest failure mode, overconfidence_and_hallucination, task_category

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.223 →

Feedback