{"version":"2.1.317","anchor":"remote-session-message-send-flow-reworked-with-a-held-send","canonical_anchor":"remote-session-message-send-flow-reworked-with-a-held-send","heading":"Remote Control handles held messages and session titles differently","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-session-message-send-flow-reworked-with-a-held-send","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remote Control handles held messages and session titles differently\n\nIn remote sessions, some held-back messages now fail without a warning, and auto-titling skips a session whose name was changed\n\n**What**\n\nRemote Control lets you drive a Claude Code session that is running somewhere else. Three things about how it sends messages changed:\n\n- A message held back for a particular reason now fails quietly, with no warning notice. Before, any failed send showed a notice or warning.\n\n- The automatic title for a session is now tied to the message it came from. It can be called off, and it is skipped if the remote session's name was changed.\n\n- Cancelling a request can now say that no turn is running. A turn is one round of Claude working on your message.\n\n**Why**\n\nWhat you see when a send is held back is different: some of those sends no longer show a notice. A name you gave a remote session is not replaced by an automatic title.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}