Feedback now lets you tag a failure mode and task category, cycled with the arrow keys.
What's wrong with this entry?
SendFeedback drafts, the review UI, the rendered feedback body and two telemetry events all gained failure_mode and task_category classification.
failure_modeis a closed list of 16 model-behaviour issues includinginstruction_following,destructive_actions,repetition_and_looping,overconfidence_and_hallucination,stopping_short,overeager,subagent_overspawn,tone_or_preachinessandothertask_categoryis one ofcode_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_submittednow reports both fields
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Survey follow-ups carry their context into /feedback for 30 seconds
Both mention feedback
-
v2.1.235
Bug reports are trimmed to fit an 8 MiB upload limit
Both mention feedback
-
v2.1.235
Bug reports that are too large drop the transcript automatically
Both mention feedback