{"version":"2.1.236","anchor":"peer-idle-notices-are-batched-and-capped","canonical_anchor":"peer-idle-notices-are-batched-and-capped","heading":"Peer idle notices are batched and capped","tier":"notice","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/peer-idle-notices-are-batched-and-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Peer idle notices are batched and capped\n\nIdle-peer notices are batched and capped so they cannot flood your terminal.\n\n**What**\n\nNotices about idle peer sessions are now collected rather than printed one at a time: they are held for 500ms, flushed early once 50 pile up, and limited to 10 shown per rolling minute with the rest collapsed into a summary line.\n\n**Details**\n\n- Notices whose session no longer matches the current conversation are dropped if you clear the conversation inside the batching window.\n- Notices that arrived before the view mounted are replayed, also capped at 10 with the remainder summarised.\n- The batching is wired into the REPL unconditionally; what decides whether peer idle notices are produced at all sits outside this code.\n\n**Evidence**\n\n`recorded in the last minute.`\n\n- Area: Cross-Session Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}