{"version":"2.1.317","anchor":"remote-session-turn-state-handling-reworked-forgetline-on","canonical_anchor":"remote-session-turn-state-handling-reworked-forgetline-on","heading":"Cloud and remote sessions track whether a reply is in progress differently","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-session-turn-state-handling-reworked-forgetline-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Cloud and remote sessions track whether a reply is in progress differently\n\nClaude Code reworked how remote sessions track a running reply, and the 'You took your first message back' notice now covers one more case\n\n**Unclear.** It is not clear what you will see differently, or what the second situation for the 'took your first message back' notice is.\n\n**What**\n\nIn a remote or cloud session, which is a session where Claude runs on another machine, Claude Code has reworked how it tracks whether Claude is still working on a reply. It now handles a reply that was stopped partway through, and it resets some of this tracking when the session connects or reconnects.\n\nThe way Claude Code clears a first message that was held back and then taken back has also changed. The notice 'You took your first message back. It wasn't sent to the cloud session.' now appears in a second situation as well as the original one.\n\n**Why**\n\nIn practice this affects the busy indicator and the turn tracking you see in cloud and remote sessions, and when you are told that a first message was not sent.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}