{"version":"2.1.246","anchor":"input-arriving-after-a-remote-stream-closes-is-dropped-inste","canonical_anchor":"input-arriving-after-a-remote-stream-closes-is-dropped-inste","heading":"Input arriving after a remote stream closes is dropped instead of throwing","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/input-arriving-after-a-remote-stream-closes-is-dropped-inste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Input arriving after a remote stream closes is dropped instead of throwing\n\nTyping after a remote session's stream closes is discarded rather than throwing an error.\n\n**What**\n\nIn remote sessions, terminal input was written straight into the session stream and could throw if the stream had already closed. Writes now check first and are silently discarded once it has ended.\n\n**Details**\n\n- The first drop on each input channel is reported once with the channel name, which is `stdin` for terminal input; later drops are silent.\n- Applies to all remote transports with no setting to change it.\n\n**Evidence**\n\n`cli_remote_io_inbound_dropped_after_close`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}