{"version":"2.1.287","anchor":"background-session-reply-refused-when-worker-version-differs","canonical_anchor":"background-session-reply-refused-when-worker-version-differs","heading":"Replies to background sessions are refused when they cannot be delivered safely","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-session-reply-refused-when-worker-version-differs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Replies to background sessions are refused when they cannot be delivered safely\n\nA reply to a background session on a different Claude Code version now goes only through a direct connection or is refused\n\n**Unclear.** Exactly what the version check tests is not known.\n\n**What**\n\nA background session is a Claude Code session running on its own while you do other things. When you send it a reply and the version of Claude Code that started it fails a check against your current version, the reply now goes only through a direct connection to that session. If that connection is missing, not connected, or was refused, the reply is refused and a line is written to the log. Before, the reply was typed into the session's terminal instead.\n\nThis applies to background sessions that were not started to run a single command.\n\n**Why**\n\nReplies to background sessions can now be refused where they used to be sent, so a reply that seems to do nothing may have been turned away.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}