{"version":"2.1.285","anchor":"background-session-reply-supports-nextturn","canonical_anchor":"background-session-reply-supports-nextturn","heading":"Replies to background sessions can now wait for the next turn","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/background-session-reply-supports-nextturn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Replies to background sessions can now wait for the next turn\n\nReplies to a background session can be marked for its next turn, and a reply to a blocked session is no longer typed into its terminal\n\n**Unclear.** It is not clear which part of Claude Code sends these replies or how a reader would use the next-turn option.\n\n**What**\n\nA background session is a Claude Code conversation that keeps running without being on your screen. Sending it a reply now accepts an option that saves the reply for the session's next turn. A reply sent this way always goes through Claude Code's own message channel rather than being typed into the session's terminal.\n\nIf the session is blocked, meaning it is waiting on something, and it is not running in exec mode, the reply is no longer typed into its terminal. Claude Code reports that the reply was not delivered.\n\n**Why**\n\nReplies to a background session can now wait for its next turn instead of being typed in while it is busy.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}