Fj!UdZddlmZddlZddlZddlZddlZddlZddlZddl m Z ej e Z ejZdaded<ehdZdddZd dZd!dZd!dZd"dZd#dZddd$dZd%dZdS)&uWLocal-environment toolchain probe for the system prompt. When the terminal backend is local (the agent's tools run on the same machine as Hermes itself), we surface a single deterministic line about Python tooling state so models don't have to discover it by hitting walls. Common failure modes this addresses: * Hermes ships under one Python (e.g. 3.11 in a bundled venv) while the user's login shell has a different one (e.g. 3.12 system). ``pip`` resolved from PATH may not match ``python3 -m pip``. * The bundled-venv Python has no pip module installed → ``python3 -m pip`` returns ``No module named pip``. * The system Python is PEP-668 externally-managed → naive ``pip install`` fails with ``error: externally-managed-environment``. The probe is cheap (a handful of subprocess calls, ~50ms total), cached for the lifetime of the process, and emits **at most one short line** when something non-default is detected. When the environment looks normal (python3+pip both present and matched, no PEP 668), it emits nothing — no token cost. Remote terminal backends (docker, modal, ssh, …) are skipped: the host's Python state is irrelevant when tools run inside a sandbox. The sandbox has its own existing probe (``_probe_remote_backend``) in ``agent/prompt_builder.py``. Toggle via ``agent.environment_probe`` in config.yaml (default True). ) annotationsN)Optional Optional[str] _CACHED_LINE>sshmodaldockerdaytona singularity managed_modal@cmd list[str]timeoutfloatreturntuple[int, str, str]c& tj|dd|d}|j|jpd|jpdfS#t $rYdStj$rYdSt$r}ddd|fcYd }~Sd }~wwxYw) zRun a short subprocess. Returns (returncode, stdout, stderr). Failures (binary missing, timeout, OSError) return (-1, "", ""). TF)capture_outputtextrcheck)rz not found)rrrrz oserror: N) subprocessrun returncodestdoutstripstderrFileNotFoundErrorTimeoutExpiredOSError)rrresultexcs ./usr/local/lib/hermes-agent/tools/env_probe.py_runr&8s )      6=#6B"="="?"?&-BUSUA\A\A^A^^^ ###"""  $!!!   )))2(3((((((((()s*AA B$B5 B>B B Bbinarystrcrtj|sdSt|ddg\}}}|dkr|r|SdS)zFReturn a short version string like ``3.12.4`` for ``binary``, or None.N-cz`import sys; print(f'{sys.version_info.major}.{sys.version_info.minor}.{sys.version_info.micro}')rshutilwhichr&)r'rcouterrs r%_python_version_ofr1NsW <  t(JKLLLBS Qww3w 4boolchtj|sdSt|dddg\}}}|dkS)z/True if `` -m pip --version`` succeeds.Fz-mpip --versionrr+)r'r._out_errs r%_has_pip_moduler9Xs> <  u64 <==NBd 7Nr2ctj|sdSd}t|d|g\}}}|dko|dkS)zTrue when ````'s install location is PEP-668 externally-managed. Looks for ``EXTERNALLY-MANAGED`` next to the stdlib (the marker file Debian/Ubuntu drop in to gate naive ``pip install``). Fzimport sys, os;stdlib = os.path.dirname(os.__file__);marker = os.path.join(stdlib, 'EXTERNALLY-MANAGED');print('yes' if os.path.exists(marker) else 'no')r*ryes)r,r-r&r)r'coder.r/r8s r%_detect_pep668r=`s] <  u ; &$-..MBT 7 +syy{{e++r2cDtjdsdStddg\}}}|dks|sdSd|vrf|drQ |ddd}|ddS#t tf$rYdSwxYwdS) zIf ``pip`` is on PATH, return the Python version it's bound to. ``pip --version`` output looks like:: pip 24.0 from /usr/lib/python3/dist-packages/pip (python 3.12) Returns the parenthesised version (e.g. ``"3.12"``) or None. r5Nr6rz(python )r)r,r-r&endswithrsplitr IndexErrorAttributeError)r.r/r8tails r%_pip_python_versionrFrs <  t%-..MBT QwwcwtSS\\#.. ::j!,,Q/D9??$$ $N+   44  4s7BBBctjdpd}|tvrdSt d}t d}|rt dnd}t}|rtdnd}tj ddu}t|o|o| | }|duo |o| o| p|}|rdSg} |r"d |} |s| d z } | | n| d |r||kr| d |n|s|r| d |r7|r| d|dn3|s| d|n|rn| d|r| d|r| d| sdSdd| zdzS)uBuild the one-liner. Returns "" when nothing notable is detected. Emit only when SOMETHING is off — the goal is to save the model from hitting an avoidable wall, not to narrate a healthy environment. TERMINAL_ENVlocalrpython3pythonFuvNzpython3=z (no pip module)zpython3=missingzpython=zpython=missing (use python3)u pip→pythonz (mismatch)z pip=missingzPEP 668=yes (use venv or uv)z uv=installedzPython toolchain: z, .)osgetenvrlower_REMOTE_BACKENDSr1r9rFr=r,r-r3 startswithappendjoin) backendpy3_verpy_ver py3_has_pip pip_bound_to py3_pep668has_uvmismatchsilent_conditionsbitspy3_bits r%_build_probe_liner`sy((3G::<<BBDDG"""r ++G  ) )F07B/),,,UK&((L.5@ ***5J \$  t +F LUWUW5G5G 5U5U1UVVHt '  'L '^ %v  rD'&W&& * ) )G G %&&& 4&G## &f&&'''' 44 2333 #  7 KK@|@@@ A A A A 7 KK5|55 6 6 6 #  M"""4 2333 $ N### r $))D// 1C 77r2F) force_refreshracj|r!t5dadddn #1swxYwYttSt5ttcdddS t}n4#t$r'}td|d}Yd}~nd}~wwxYw|a|cdddS#1swxYwYdS)u$Return the cached probe line (building it on first call). Returns "" when the environment is clean — the system prompt assembler should drop the section in that case rather than emit an empty heading. ``force_refresh`` is for tests; real callers should never need it. Nzenv_probe failed: %sr) _CACHE_LOCKrr` Exceptionloggerdebug)raliner$s r%get_environment_probe_linerhst   L                    #         $&&DD    LL/ 5 5 5DDDDDD                    sGB(A$#B($ B.B B(BB((B,/B,NonecJt5daddddS#1swxYwYdS)u8Test helper — clear the cache between probe scenarios.N)rcrr2r%_reset_cache_for_testsrlss  s )r )rrrrrr)r'r(rr)r'r(rr3)rr)rr()rar3rr()rri)__doc__ __future__rloggingrNr,rsys threadingtypingr getLogger__name__reLockrcr__annotations__ frozensetrQr&r1r9r=rFr`rhrlrkr2r%rxs:#"""""    8 $ $ in " """" 9 ))))),,,,,$0I8I8I8I8X9>:r2