{"version":"2.1.318","anchor":"remote-sessions-give-up-waiting-for-the-workers-start-up-li","canonical_anchor":"remote-sessions-give-up-waiting-for-the-workers-start-up-li","heading":"Remote sessions stop waiting for a silent worker and send your queued messages","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-sessions-give-up-waiting-for-the-workers-start-up-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote sessions stop waiting for a silent worker and send your queued messages\n\nIf a remote session's worker never sends a readable start-up message in time, Claude Code stops waiting and sends your queued messages\n\n**What**\n\nIn a remote session, your messages are handled by a worker on another machine. While Claude Code waits for that worker to start, messages you type are held in a queue. Claude Code now starts a timer when it first sees a start-up line or worker message. If nothing it can read arrives in time, it stops waiting and sends the queued messages. It also records how many messages were waiting.\n\n**Why**\n\nA remote session whose worker never reports in no longer leaves your typed messages stuck in the queue indefinitely.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}