Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
Unclear What stdinLane does and how it affects remote session behavior is not specified in the finding.
What
The class driving a remote (bridge/cloud) session's stream-json IO now accepts a new stdinLane constructor option, alongside the existing streamUrl, initialPrompt, sessionState, and similar options. The SDK's query() function, which builds either a local or remote-controlled query stream, now keeps the initial string prompt separate from a raw async-iterable/generator input, passing the latter through as this new stdinLane rather than always coercing all input into a single combined async generator.
Why
Separating the initial prompt from ongoing stdin input lets remote/bridge sessions handle streamed input more flexibly instead of forcing everything through one merged stream.
