Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Feedback survey: follow-up text results and a narrower every_rating

The feedback survey can now report follow-up text results with a logs_followup signal, and every_rating needs one more condition

Group of 2 Under the hood Internal Changes
JSON All of v2.1.310
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.310,
Internal ChangesSection of the release

What

After you rate a response, Claude Code can show a feedback survey with a box for more comments. A host is an app that runs Claude Code inside it, such as an editor. Several pieces of this changed:

  • Follow-up details: the survey record a host sends now carries followup_box, no_followup_reason, char_count, error_code and saved_locally.
  • Follow-up events: followup_text_submitted and followup_text_failed are now accepted, and are handled before the usual survey check.
  • logs_followup: a new field tells hosts whether this version logs the followup_* survey events they send. The feedback and transcript-sharing information now always includes logs_followup: true.
  • every_rating: this value, which marks every rating for collection, now needs one more value to be present on top of the tengu_curried_sparrow server switch.

The previous release built tengu_curried_sparrow as off by default, and no reading has been taken under this release yet.

Why

An editor's feedback box can now report whether follow-up text was sent, saved or failed. Every rating is marked for collection in fewer cases than before.

See this entry in the whole of v2.1.310 →

Feedback