{"version":"2.1.221","anchor":"sendfeedback-per-session-caps-are-remote-configurable","canonical_anchor":"sendfeedback-per-session-caps-are-remote-configurable","heading":"SendFeedback per-session caps are remote-configurable","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/sendfeedback-per-session-caps-are-remote-configurable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### SendFeedback per-session caps are remote-configurable\n\nHow often Claude can send feedback or draft prompts per session is now tunable server-side.\n\n**What**\n\nThe limits on how often the feedback tool can be called and how many draft prompts it can produce in a session can now be adjusted server-side.\n\n**Details**\n\n- Read from the existing `tengu_juniper_relay_config` payload via new `maxToolCallsPerSession` and `maxDraftPromptsPerSession` keys.\n- Clamped to 1 to 50 and 0 to 20, with defaults 10 and 3 when the config is absent.\n- The cap value is included in the capped-call telemetry and in the message Claude sees.\n\n**Evidence**\n\n`maxToolCallsPerSession`\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"}