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.233 Home All releases olderv2.1.232 v2.1.234newer
Claude Code v2.1.233

New inbound relay origin treated as a human turn

You'll notice
Useful2 Signal4
Relay

Relayed messages from a new inbound source count as a human turn by default.

Feature flag
tengu_cuddly_willow Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

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

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.233. It isn't a statement about your account. What a flag value here can and cannot tell you

What

Relay message classification gained an origin named "hearth_human", counted as a human turn only when a gate allows it. The gate reads the remote flag tengu_cuddly_willow, which falls back to true, so with no remote value set the origin is honoured.

Details
  • Two telemetry events accompany it: "bridge_projects_human_origin" when the origin is accepted, and the same name logged as rejected with reason "disabled_by_flag" when the gate is off.
  • Neither the origin nor the gate name existed in the previous build.
Evidence

bridge_projects_human_origin

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