{"version":"2.1.233","anchor":"new-inbound-relay-origin-treated-as-a-human-turn","canonical_anchor":"new-inbound-relay-origin-treated-as-a-human-turn","heading":"New inbound relay origin treated as a human turn","tier":"notice","area":"Relay","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/new-inbound-relay-origin-treated-as-a-human-turn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### New inbound relay origin treated as a human turn\n\nRelayed messages from a new inbound source count as a human turn by default.\n\n**What**\n\nRelay 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.\n\n**Details**\n\n- 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.\n- Neither the origin nor the gate name existed in the previous build.\n\n**Evidence**\n\n`bridge_projects_human_origin`\n\n- Flag `tengu_cuddly_willow`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.233; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: Relay\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5"}