{"version":"2.1.228","anchor":"rate-limit-state-is-published-to-remote-sessions","canonical_anchor":"rate-limit-state-is-published-to-remote-sessions","heading":"Rate-limit state is published to remote sessions","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/rate-limit-state-is-published-to-remote-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Rate-limit state is published to remote sessions\n\nRemote viewers of your session now see the same rate-limit state you do.\n\n**What**\n\nRate-limit updates are now attached to session metadata as `rate_limit_info` for bridged and print-mode sessions, so a remote viewer sees the same limit state as the local session.\n\n**Details**\n\n- Publishes are de-duplicated per target, and a window that has already expired is cleared rather than sent.\n- The publish is wrapped so a failure only logs instead of breaking the rate-limit listener.\n\n**Evidence**\n\n`rate_limit_info`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}