{"version":"2.1.290","anchor":"peer-reply-can-run-immediately-in-background-review-interru","canonical_anchor":"peer-reply-can-run-immediately-in-background-review-interru","heading":"Changes to how queued messages and interruptions are handled","tier":"notice","area":"Messaging","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/peer-reply-can-run-immediately-in-background-review-interru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Changes to how queued messages and interruptions are handled\n\nSome peer replies during background review now run at once instead of waiting in a queue, and the interruption check is simpler\n\n**Unclear.** It is not clear what difference these changes make to what a user sees.\n\n**What**\n\nSeveral changes affect how Claude Code holds and delivers messages while it is busy:\n\n- A reply from a peer during a background review can now run at once. Before, every such reply waited in a queue.\n\n- The check that decides whether a message may interrupt current work now only looks at whether the message was sent to go out immediately. It no longer considers where the message came from, its priority or whether it was waiting.\n\n- A session in a state where no model turn will run no longer starts the part that wakes the session up to deliver messages.\n\n**Why**\n\nThese change when waiting messages are delivered and when they interrupt work in progress.\n\n- Area: Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}