{"version":"2.1.234","anchor":"the-stdin-transport-now-answers-the-remote-transport-questio","canonical_anchor":"the-stdin-transport-now-answers-the-remote-transport-questio","heading":"The stdin transport now answers the remote-transport questions","tier":"internal","area":"Transports","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/the-stdin-transport-now-answers-the-remote-transport-questio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### The stdin transport now answers the remote-transport questions\n\nPlain stdin sessions now declare they are not remote, so remote-only delivery acks and one auto-mode capability skip out.\n\n**What**\n\nThe plain stdin transport declares that it is not a remote transport, that the host owns the origin of anything arriving on stdin (used to decide whether an inbound message counts as user-driven), and that a confirmed flush always succeeds. Remote-session code branches on that: delivery acks bail out with \"not-remote-session\", and one auto-mode capability requires a remote transport plus the remote session id.\n\n**Evidence**\n\n`hostOwnsStdinOrigin`\n\n- Area: Transports\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}