{"version":"2.1.283","anchor":"sse-transport-now-handles-an-owner-present-event-but-noth","canonical_anchor":"sse-transport-now-handles-an-owner-present-event-but-noth","heading":"Remote sessions can recognise an 'owner present' signal, but nothing acts on it yet","tier":"soon","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/sse-transport-now-handles-an-owner-present-event-but-noth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Remote sessions can recognise an 'owner present' signal, but nothing acts on it yet\n\nThe connection used by remote sessions now recognises an \"owner present\" message type, though no part of Claude Code responds to it yet\n\n**Unclear.** Whether some indirect route installs the handler after all is not ruled out.\n\n**What**\n\nRemote sessions receive a stream of short-lived messages from the server. Before, the only such message Claude Code accepted was a heartbeat check, and anything else was logged as unexpected.\n\nIt now also recognises a message called `owner_present`, and can pass it on to a handler if one has been set. No part of Claude Code sets that handler, so in practice the message is still logged as an unexpected type.\n\n**Why**\n\nThis is the receiving end of a signal that the user who owns a remote session is present. It has no visible effect yet and looks like groundwork for later.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}