Source Intelligence

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.223 Home All releases olderv2.1.222 v2.1.224newer

Feedback drafts can be reviewed and sent through the SDK control protocol

Not switched on
Useful2 Signal3
Feedback Notable not in their notes

Saved feedback drafts can be reviewed and sent over the SDK, but the surface is off by default.

Draft-based submit_feedback handling is fully wired, but the feedback surface sits behind tengu_juniper_relay, which falls back to false.

Feature flag
tengu_juniper_relay On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: off · compiled default in v2.1.223: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.223. It isn't a statement about your account. What a flag value here can and cannot tell you

submit_feedbackdraft_idattach_transcript
What

The submit_feedback control request can now point at a draft saved on disk, so the upload matches the consent form the user actually saw.

Details
  • the request schema gained draft_id, type, title, area and attach_transcript
  • with a draft id the handler reads the stored draft from ~/.claude/feedback/drafts/, rebuilds the description, bundles that draft's own transcript according to attach_transcript (default true), and deletes the draft on success
  • caller-supplied fields override the stored draft
  • a new feedback_draft_queued system message carrying draft_id, draft_type, title and a details preview is emitted when Claude queues a draft locally, and it was added to the system subtypes that are not treated as ordinary transcript output
  • the feedback surface itself is behind Je("tengu_juniper_relay", !1), which falls back to false absent a remote value
Evidence

UUID of a local SendFeedback draft under ~/.claude/feedback/drafts/., UUID of the on-disk draft file under ~/.claude/feedback/drafts/

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 →