{"version":"2.1.233","anchor":"remote-io-writes-inbound-data-directly","canonical_anchor":"remote-io-writes-inbound-data-directly","heading":"Remote IO writes inbound data directly","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/remote-io-writes-inbound-data-directly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Remote IO writes inbound data directly\n\nRemote input is written straight through, dropping the guard for writes after close.\n\n**What**\n\nThe remote transport now pushes received server events and piped stdin straight into the input stream. The wrapper that guarded against writes arriving after the stream closed, and the telemetry event it fired once per lane when that happened, are both gone.\n\n**Evidence**\n\n`[remote-io] keep_alive sent`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}