{"version":"2.1.283","anchor":"ccr-client-ignores-no-subscribers-reports-just-after-inbou","canonical_anchor":"ccr-client-ignores-no-subscribers-reports-just-after-inbou","heading":"Remote sessions stop dropping live output right after a viewer sends something","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/ccr-client-ignores-no-subscribers-reports-just-after-inbou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Remote sessions stop dropping live output right after a viewer sends something\n\nClaude Code now ignores a \"nobody is watching\" report that arrives just after it received something from a viewer, so live output keeps flowing\n\n**Unclear.** How long the window after incoming traffic lasts is not known.\n\n**What**\n\nIn a remote session, Claude Code streams its output in small pieces to anyone watching, and the server tells it whether anyone is watching. If that report says nobody is watching but Claude Code received something from a viewer only moments ago, it now treats the report as unknown instead of believing it.\n\n**Why**\n\nPeople viewing a cloud or remote session should see fewer missing or delayed pieces of live output when an out-of-date report arrives.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}