{"version":"2.1.287","anchor":"remote-session-send-watchdog-replaces-response-timeout-wit","canonical_anchor":"remote-session-send-watchdog-replaces-response-timeout-wit","heading":"Remote Control watches for slow responses and reconnects","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-session-send-watchdog-replaces-response-timeout-wit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote Control watches for slow responses and reconnects\n\nAfter a send, Remote Control now uses a watch that reconnects on timeout and shows a notice if it cannot be set up\n\n**Unclear.** It is not clear how the new watch differs from the old timer beyond the notice.\n\n**What**\n\nIn Remote Control, after a message is sent to the remote session, Claude Code waits for a response and reconnects if none comes in time. It used a plain timer for this. It now uses a watch that reconnects on timeout, and shows a notice if the watch cannot be set up.\n\nMessages that must be sent together can now be tied so they go out in the same batch.\n\n**Why**\n\nThis affects how Remote Control recovers when a response is slow, and tells you when that safeguard is not in place.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}