{"version":"2.1.287","anchor":"session-notices-can-be-typed-fields-keep-awake-during-bridg","canonical_anchor":"session-notices-can-be-typed-fields-keep-awake-during-bridg","heading":"Remote sessions keep the machine awake during turns and can stop a turn to send queued messages","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/session-notices-can-be-typed-fields-keep-awake-during-bridg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote sessions keep the machine awake during turns and can stop a turn to send queued messages\n\nRemote turns now hold the machine awake, and a remote send-now request can stop a running turn when messages are queued\n\n**Unclear.** It is not clear what setting, if any, controls the keep-awake hold.\n\n**What**\n\nThree changes affect sessions driven remotely, where another device or service sends work to Claude Code on your machine:\n\n- Keep-awake: while a remote turn is running, Claude Code holds the machine awake. A turn is one round of Claude working on a request.\n\n- Send now: a remote \"send now\" request can now cancel the turn that is running when queued messages are waiting to go in.\n\n- Session notices: the text of session notices can now be built in a second, more structured way, but that way is switched off in the code.\n\n**Why**\n\nA machine that stays awake does not drop a remote turn halfway through. Being able to stop the current turn means messages you queued remotely are not left waiting behind it.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}