{"version":"2.1.221","anchor":"juniper-feedback-relay-is-configured-remotely","canonical_anchor":"juniper-feedback-relay-is-configured-remotely","heading":"Juniper feedback relay is configured remotely","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/juniper-feedback-relay-is-configured-remotely","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Juniper feedback relay is configured remotely\n\nThe feedback relay tool's wording and per-session limits can now be set from the server instead of hardcoded.\n\n**What**\n\nThe feedback-relay tool's description, prompt and per-session limits are now supplied by server config rather than hardcoded.\n\n**Details**\n\n- description and prompt come from the `tengu_juniper_relay_config` payload, falling back to built-in text when the value is absent or empty\n- `maxToolCallsPerSession` is validated as an integer with a minimum of 1\n- `maxDraftPromptsPerSession` is validated as an integer with a minimum of 0\n- both are clamped to a built-in default and an upper bound\n- absent a server value the built-in description, prompt and default limits are used\n\n**Evidence**\n\n`tengu_juniper_relay_config`\n\n- Flag `tengu_juniper_relay_config`: Not enough to say (read for one account on one subscription tier against v2.1.221; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}