{"version":"2.1.315","anchor":"worker-movesbash-flag-and-candeliveroverturn-for-send-now","canonical_anchor":"worker-movesbash-flag-and-candeliveroverturn-for-send-now","heading":"Remote workers send a new shell setting, and sent-now messages can arrive mid-turn","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/worker-movesbash-flag-and-candeliveroverturn-for-send-now","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote workers send a new shell setting, and sent-now messages can arrive mid-turn\n\nRemote workers now pass a setting about shell commands, and in non-interactive mode a send-now message can be delivered during a turn\n\n**Unclear.** What the new shell setting changes in practice is not known.\n\n**What**\n\nTwo related changes affect sessions run by a remote worker, a separate process that runs the session for Claude Code:\n\n- The worker's startup message can now carry a setting saying whether the worker moves shell commands. Before, only the setting for sending messages right away was read.\n\n- In non-interactive mode, where Claude Code handles a request without a chat screen, a message marked to be sent right away can now be delivered during a turn. This applies while the conversation is being compacted (shortened to save space), or when a saved copy of the conversation already holds content.\n\n**Why**\n\nQueued messages and shell commands that run in the background may behave differently when a remote worker runs the session.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}