+ lHj&+a0t$Rt^RIHt^RIt^RIt^RIt^RIt^RIt^RI H t H t ^RI H t ]P!]4tRRRR/RR lltR R ltR R ltRRltRRRR/RRlltRRltRRRRRR/RRlltRRRRR]P0/RRlltRRRRRRRR/R R!lltR"t/tR#]R$&]P<!4t!R%R&4t R'R(RR/R)R*llt!R#)+aA long-lived process INSIDE a terminal backend with both stdio pipes open. ``BaseEnvironment.execute`` is request/response: it captures output and returns. The desktop that follows the terminal backend needs three things that are not: the RFB byte stream between the Desktop pane and the sandbox's Xvnc, cua-driver's MCP-over-stdio server, and agent-browser invocations whose daemon must outlive the call. All three are "spawn argv in the sandbox, keep stdin/stdout as pipes". Each spawn-per-call backend has a local argv prefix that gives exactly that (``docker exec -i``, ``ssh``); this module is the one place that knows them. SDK backends (modal, daytona, vercel) have no argv prefix: ``exec_prefix`` returns None there and the desktop stays on the gateway host (or refuses, per ``bot_desktop.placement``). Plugin backends that declare ``supports_streams`` supply the prefix from their environment's own ``exec_prefix()``. ) annotationsN)OptionalSequence)BaseEnvironmentuser interactiveTc(V^8dQhRRRRRRRR/# envrr Optional[str]rboolreturnOptional[list[str]])formats"?/home/ubuntu/.hermes/hermes-agent/tools/environments/streams.py __annotate__rs0HH_H}HRVHbuHcL^RIHp^RIHp\ W4'd[\ VRR4pV'gR#VP R.pV'dVPR4V'd VRV., pWe.,#\ W4'dVP4#\WVR7#) zLocal argv that runs its remainder inside ``env``, or None for backends without one. ``user`` selects the sandbox-side account (docker only; ssh runs as the configured login). ``interactive`` keeps stdin open (``docker exec -i``); ssh always does. )DockerEnvironmentSSHEnvironment _container_idNexecz-iz-urr) tools.environments.dockerrtools.environments.sshr isinstancegetattr _docker_exeappend_build_ssh_command_plugin_exec_prefix)r rrrr containerargvs&$$ r exec_prefixr&s <5#))C$7 (  KK   T4L Dk!!#&&%%'' s; GGrc(V^8dQhRRRRRRRR/#r r)rs"rrr4s***_*}*SW*\o*rc\VRR4p\V4'gR#V!WR7pT'gR#\T\\34'g@\P R\ T4P \ T4P 4R#TUu.uFp\T4NK up# \d0\P R\ T4P RR7R#i;iuupi)z`A plugin environment's own ``exec_prefix()`` (``TerminalEnvironmentProvider.supports_streams``).r&NrzA%s.exec_prefix() failed; treating the backend as unable to streamT)exc_infoz`%s.exec_prefix() returned %s, not a list of argv words; treating the backend as unable to stream) rcallable Exceptionloggerwarningtype__name__rlisttuplestr)r rrhookprefixparts&$$ rr#r#4s 3 t ,D D>>49  ftUm , ,#$(I$6$6V 8M8M O"( )&$CI& )) ZCy))D  : *s B+C(+6C%$C%c V^8dQhRRRR/#)r r rrr2r)rs"rrrIsEE/EcErcb\VRR4p\V4'd\V!44#R#)zg``env.get_temp_dir()``, or ``/tmp`` for a plugin environment that doesn't subclass ``BaseEnvironment``. get_temp_dirNz/tmp)rr*r2)r r8s& rsandbox_temp_dirr9Is,35L"*<"8"83|~ DfDrc V^8dQhRRRR/#r r rrr r)rs"rrrOs::/:d:rc \VRR7RJ#)T)rN)r&)r s&rsupports_streamsr=Os s -T 99rr shell_joinedFc ,V^8dQhRRRRRRRRRR /#) r r4 Sequence[str]r%r Optional[dict]r>r rz list[str]r)rs"rrrSs1 + + +] +N +" +/8 +rcRPRT;'g/P444pV RRPRV44 2pV'd.VO\P!RRV.4N#.VORNRNVN#)aA``prefix`` + a ``bash -c`` that exports ``env`` and execs ``argv``. The script is built once, then delivered the way the client needs it: argv-preserving clients (docker, apptainer) get ``["bash", "-c", script]``; ``shell_joined`` clients (OpenSSH joins the words after the host with spaces and the remote login shell splits them again) get the whole ``bash -c '