{"version":"2.1.319","anchor":"feedback-relay-gate-now-also-requires-a-non-gateway-provider","canonical_anchor":"feedback-relay-gate-now-also-requires-a-non-gateway-provider","heading":"Feedback relay now stays off when you use a gateway provider","tier":"notice","area":"Feedback","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/feedback-relay-gate-now-also-requires-a-non-gateway-provider","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Feedback relay now stays off when you use a gateway provider\n\nSending feedback through the relay that CLAUDE_CODE_SEND_FEEDBACK turns on is now off when Claude Code runs through a gateway\n\n**What**\n\nThe feedback relay, turned on with `CLAUDE_CODE_SEND_FEEDBACK`, now also stays off when Claude Code reaches the model through a gateway, a service placed between Claude Code and the model. Elsewhere it still depends on a remote switch that falls back to off. That switch read on for this site's account and off for an anonymous one in a reading taken before this release.\n\n**Why**\n\nIf you use a gateway provider, setting `CLAUDE_CODE_SEND_FEEDBACK` does not turn the relay on.\n\n- Flag `tengu_juniper_relay`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.319; this account: on, anonymous baseline: off, compiled default: 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.\n- Area: Feedback\n- Names: `CLAUDE_CODE_SEND_FEEDBACK`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}