{"version":"2.1.287","anchor":"background-session-reply-goes-through-the-rendezvous-for-new","canonical_anchor":"background-session-reply-goes-through-the-rendezvous-for-new","heading":"Replies to background sessions are routed differently for newer workers","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-session-reply-goes-through-the-rendezvous-for-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Replies to background sessions are routed differently for newer workers\n\nReplies to a background session now go straight to the session when its worker is new enough, and refusals are logged with a reason\n\n**Unclear.** It is not clear which worker versions qualify for the new route.\n\n**What**\n\nWhen you reply to a session running in the background, Claude Code previously read the session's state file and fell back to typing into its terminal. It now sends the reply straight to the session when the background worker's version qualifies, and logs the reason when a reply is refused. A session whose interactive prompt is waiting for input is now treated as blocked.\n\n**Why**\n\nThis changes how replies reach background sessions, which should make delivery to newer workers more direct.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}