{"version":"2.1.265","anchor":"session-stdin-handling-split-by-connection-lane","canonical_anchor":"remote-io-stdin-now-explicitly-warns-and-is-ignored-outside","heading":"Remote session stdin is now split by connection lane","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/session-stdin-handling-split-by-connection-lane","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote session stdin is now split by connection lane\n\nRemote sessions now only treat stdin as real input on bridge\/BYOC connections, discarding and warning on it otherwise\n\n**What**\n\nRemote session IO setup no longer pumps all inbound stdin (standard input, the text stream a program reads from) through a single loop. It now dispatches to one of two lanes:\n\n- `pumpStdinLane`, used for `bridge` or `byoc` (bring-your-own-compute) host connections, where stdin is a real input source.\n\n- A new `discardStdinLane`, used otherwise, which drains and discards any data arriving on stdin and logs a warning the first time non-empty data appears, explaining that control input for other host types comes from the session stream instead.\n\n**Why**\n\nThis prevents stray or unexpected stdin data from being silently treated as real input on connection types where it was never meant to be one, while still making it visible via a warning if it happens.\n\n- Area: Sessions\n- Names: `pumpStdinLane`, `discardStdinLane`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}