+ lHj?Rt^RIHt^RIt^RIHt^RIHtHt]P!] 4t Rt Rt RtRt]!RR 7!R R 44tR R ltRRltRRltRRltRRltRR/RRlltR#)aWhere this profile's desktop lives: the gateway host or inside the configured terminal backend. ``bot_desktop.placement``: ``auto`` (default) follow the terminal backend when it is a sandbox that can host a stream (docker / ssh, or a plugin backend declaring ``supports_streams``); the gateway host when ``terminal.backend`` is local. A sandbox backend that CANNOT host one (modal, daytona, vercel) resolves to ``refused``: the user chose a sandbox for the agent's actions, so quietly running the screen, cua-driver and the browser on the host beside it would hand the agent a desktop outside that sandbox. ``terminal`` always the terminal backend; error when it cannot host one. ``gateway`` always the gateway host (the pre-#108914 behaviour for sandboxed users, now an explicit opt-in because it is the boundary-crossing shape). ``resolve()`` is pure config + backend-class reasoning: it never starts a sandbox. ``terminal_environment()`` does acquire the profile's terminal environment (creating the container if needed) because a screen cannot exist before the sandbox does. ) annotationsN) dataclass)AnyOptionalgatewayterminalrefusedT)frozenc:]tRt^ t$R]R&R]R&RtR]R&RtR#) PlacementstrwherebackendreasonN)__name__ __module__ __qualname____firstlineno____annotations__r__static_attributes__r@/home/ubuntu/.hermes/hermes-agent/tools/bot_desktop/placement.pyr r s J LFCrr cV^8dQhRR/#returnr r)formats"r __annotate__r'sEE#Erc^RIHpV!4PR4;'g/p\VPR4;'gR4P 4P 4pVR\ \39dV#R#))load_config_readonly bot_desktop placementauto)hermes_cli.configr"getr striplowerTERMINALGATEWAY)r"cfgvalues r_settingr.'sf6  $ $] 3 9 9rC  $.. / 5 5 7 = = ?Efh885DfDrcV^8dQhRR/#rr)rs"rrr.s==3=rc`^RIHp\V!4PR4;'gR4#)r!_get_env_configenv_typelocal)tools.terminal_toolr2r r'r1s r_terminal_backendr6.s&3  $$Z0;;G <terminal.backend is local, so the terminal IS the gateway hostzterminal.backend is a, a plugin that runs in the plugin host (plugins.isolation: host), and the host cannot hand its sandbox's exec channel to Hermes, so the screen cannot follow it. Set plugins.isolation: in_process, or bot_desktop.placement: gateway to run the desktop on the gateway host.z, which cannot host a screen yet, and running the desktop on the gateway host would put the agent's screen, browser and computer_use outside the sandbox you chose for it. Set bot_desktop.placement: gateway to allow that explicitly.) r6r r+r._STREAM_BACKENDSr*r=rDREFUSED)rsettingrs rresolverJ@s !G''+klljG''**""7++w$&&Xw/ /'"7),   %WI.UVF Wg ..rcreatec V^8dQhRRRR/#)rrKr8rz Optional[Any]r)rs"rrrYs 4 4D 4M 4rc^RIHpVPR4pVP;_uu_4VP VR4pRRR4Xf V'gV#VPRRR7VP;_uu_4VP VR4uuRRR4# +'giLb;i +'giR#;i)zThis profile's terminal environment object (the one ``terminal`` runs commands in). ``create=False`` only returns an already-running one.) terminal_toolNtrue)task_id)toolsrN_resolve_container_task_id _env_lock_lookup_active_env)rKttrPenvs$ rterminal_environmentrWYs*++D1G ##GT2  f VT* $$Wd3   sB<B, B) , B= )dockerssh)__doc__ __future__rlogging dataclassesrtypingrr getLoggerrloggerr+r*rHrGr r.r6r=rDrJrWrrrras"#!   8 $   $ $ E= A ./2 44 4 4r