{"version":"2.1.293","anchor":"defer-cap-fork-refuses-when-user-has-draft-or-an-ask-is-open","canonical_anchor":"defer-cap-fork-refuses-when-user-has-draft-or-an-ask-is-open","heading":"Moving work to the background now waits if you are typing or answering a question","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/defer-cap-fork-refuses-when-user-has-draft-or-an-ask-is-open","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Moving work to the background now waits if you are typing or answering a question\n\nClaude Code no longer hands work off to the background on a timer while you have unsent text or a question is open\n\n**What**\n\nClaude Code has a timer that, when it runs out, hands the current work off to a separate background copy of the session. Before, it did this regardless of what was on screen. Now it cancels the hand-off when:\n\n- you have typed text in the input box that you have not sent yet\n\n- a dialog or a question for you is open\n\nClaude Code also now tracks when a hand-off is already in progress, behind a separate feature check.\n\n**Why**\n\nThis stops the switch to the background from losing text you were in the middle of typing or cutting across a question you were answering.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}