{"version":"2.1.319","anchor":"fleet-reply-input-enter-handling-changed-when-a-wt-conditio","canonical_anchor":"fleet-reply-input-enter-handling-changed-when-a-wt-conditio","heading":"Fleet view reply box holds back drafts for some sessions, except \/stop","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/fleet-reply-input-enter-handling-changed-when-a-wt-conditio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Fleet view reply box holds back drafts for some sessions, except \/stop\n\nFor some sessions, the fleet view's reply box no longer acts on a non-empty draft, unless the draft is the \/stop command\n\n**Unclear.** Which sessions this applies to is not clear.\n\n**What**\n\nThe fleet view shows several Claude Code sessions at once and has a reply box for answering one. For some sessions, the reply box now stops early instead of acting on a draft that is not empty. The exception is a draft that is the command `\/stop`, which stops the current background session.\n\n**Why**\n\nThis may stop replies or commands from being sent to certain sessions, while `\/stop` still works.\n\n- Area: Background Tasks\n- Names: `\/stop`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}