{"version":"2.1.321","anchor":"bridge-poll-config-gains-forced-stops-per-hour","canonical_anchor":"bridge-poll-config-gains-forced-stops-per-hour","heading":"Server settings for the bridge can now limit forced stops per hour","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bridge-poll-config-gains-forced-stops-per-hour","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Server settings for the bridge can now limit forced stops per hour\n\nThe server-sent settings for how the bridge checks for work now accept a forced-stops-per-hour number from 0 to 60\n\n**Unclear.** What a forced stop does to a running session is not stated.\n\n**What**\n\nThe bridge is the link between Claude Code and other apps. Anthropic's servers send settings for how often it checks for new work. Those settings now accept one more value, `forced_stops_per_hour`, a whole number from 0 to 60. If the settings arrive in a form Claude Code cannot read, it falls back to built-in defaults.\n\n**Why**\n\nAnthropic can tune how many forced stops the bridge makes in an hour without shipping a new version. You cannot set this yourself.\n\n- Flag `tengu_bridge_poll_interval_config`: Not enough to say (read for one account on one subscription tier against v2.1.321; 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: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}