߲j> dZddlZddlZddlZddlZddlZddlZddlmZddl m Z m Z ddl m Z ddlmZmZmZmZddlmZddlmZdd lmZdd lmZdd lmZej@d de!e"dffdZ#de$e"fdZ%d,de"de"fdZ&de"fdZ'de"de(fdZ)de"de(fdZ*de"fdZ+de"dzde(fdZ,de e"fdZ-de"fdZ.ddd e(de"fd!Z/d-d"e0de(fd#Z1de e"fd$Z2d%e"de(fd&Z3de(fd'Z4de(fd(Z5de(fd)Z6de(fd*Z7de(fd+Z8y).u-agent-browser / Chromium discovery and install: PATH merging, npx resolution, candidate binaries, Chromium detection + auto-install, requirement checks. Split out of ``tools/browser_tool.py``. Facade-owned state is read through ``_bt`` (``tools.browser_tool``, resolved per call) — no import cycle.N)Path)ListOptional)windows_hide_flags)agent_browser_runnableget_hermes_home is_termuxnode_tool_runnable) origin_module)browser_tool_cdp)browser_tool_cloud)browser_tool_lifecycle) browser_tool_lightpanda_fallback)maxsizereturn.cd tjjrtjng}t fd|DS#t$rg}Y"wxYw)zbHomebrew versioned Node bin dirs (node@20, ...) that ``brew`` may not link into /opt/homebrew/bin.z/opt/homebrew/optc3K|]\}|jdrI|dk7rDtjjtjj |dxr^yw)nodebinN) startswithospathisdirjoin).0entrybin_dir homebrew_opts ?/home/ubuntu/.hermes/hermes-agent/tools/browser_tool_install.py z/_discover_homebrew_node_dirs..sS    F # 77==BGGLLue$LL M sA"A%)rrrlistdirOSErrortuple)entriesrrs @@r _discover_homebrew_node_dirsr&s`'L.0ggmmL.I"**\*r   s6A AAct}t}|dz dz |dz |dz dz f}gtt|t |j S)zMReturn ordered browser CLI PATH candidates shared by discovery and execution.rr node_modules.bin)_originrmapstrr&_SANE_PATH_DIRS)_bthomemanageds r _browser_candidate_path_dirsr1'sZ )C  Df}u$dVmTN5JV5STG VSg  V!=!? V#BUBU VV existing_pathcT|xsdjtjDcgc]}|s| }}g}tD]@}|s||vs ||vstjj |s0|j |Btjj||zScc}w)zLPrepend browser-specific PATH fallbacks without reordering existing entries.)splitrpathsepr1rrappendr)r3p path_parts prefix_partsparts r _merge_browser_pathr=/s+1r88DJ!JJJ L,.& D *t>$  QRWW_%P $8PQr2ctd}|r|gngdgzD]+}tjd|}|st|s)|cSy)zResolve a runnable npx, extended (Hermes-managed/Homebrew) PATH first. Bare PATH first would let a broken system npx shadow a healthy managed one, so every candidate is validated with ``node_tool_runnable`` before use. r5NrQrX)r=shutilwhichr ) extended_pathrrQs r _resolve_npx_binr^QsO (+M$1-rdVCll5t, %c*J r2r]c#(Ktjd|rtjd|ttjjdz dz }|j r#tjdt |yyw)u+Yield agent-browser lookup candidates lazily: ambient PATH → extended PATH → repo-local node_modules/.bin. The local lookup uses ``shutil.which`` with an explicit path so Windows resolves the ``.cmd`` shim (CreateProcess cannot run npm's extensionless POSIX shim — WinError 193). agent-browserrXr(r)N)r[r\r__file__parentis_dirr,)r] local_bin_dirs r _agent_browser_candidatesre_sq ,, ''ll???N))00>AFJMll?]1CDDsBBTvalidatergc t dtdtfd}dtdtf fd } jr! j |d j Srt nt}td }t|D]}|s||s||cStr| jSs td  d d l m }|d rmt}|dz dz |dz dz |dz f}dg|r|gngtt|D]1} t!j"d| } | st | s)|| cSd _|d#t$$rYwxYw)azFind the agent-browser CLI: PATH, Homebrew/managed dirs, local node_modules/.bin, npx fallback, lazy install. A bare ``shutil.which`` hit is NOT trusted: agent-browser's npm postinstall re-points a global symlink at our local node_modules binary, which vanishes on the next ``hermes update`` and leaves a dangling link ``which`` still reports (exec fails with 127). Candidates are validated with ``agent_browser_runnable`` before caching so a dead one falls through. ``validate=False`` (schema-time check_fn) only tests presence and never caches. Raises FileNotFoundError when agent-browser is not installed. cachedrc>td|rdnddtdS)Nagent-browser CLI not foundz (cached)r5z. Install it with: z) Or ensure npx is available in your PATH.)FileNotFoundErrorrAris r _not_foundz'_find_agent_browser.._not_foundxs3 #>f{Z\>]]p$9$;#<._accept|s (1C %*.C 'r2NTrmr5rkr)ensure_dependencybrowserr(r)rrr`rXF)r*boolrlr,rrrqrrYr=rer^rFhermes_cli.dep_ensurertrr+r[r\ Exception) rgrnrsokr]rortr/r0rrecheckr.s ` @r _find_agent_browserr{ms )Ci4i$5i33 ""  $ $ ,D) )(((#+ 1QB'+M.}=& I9% %&s5566  =>>  ; Y '"$Dn,v5tf}u7LdU[m\G_M-r_SQTV]M^_ , ,,TB5g>"7++ , #'C E ""    s%A#E) E5 E?E EEtimeoutcNt}t}|sy|j}t|j dd|d<t j t j d|d}tjdk(r|jtdnttt dd z|d <|d d d |jdg} t j|fdt ji|} |j!||j"d k(S#t$rYywxYw#t$rz}t%j&|t)|t j*rAt-j.t5|j!ddddn #1swYnxYwYd}~yd}~wwxYw)uBest-effort pre-fetch of the agent-browser npm package via npx (``hermes update`` / ``doctor --fix``). Runs with the credential-scrubbed env every other agent-browser spawn uses (registry-fetched npm code must never see the operator keyring), in its own process group, and tree-kills on timeout so a surviving descendant cannot hold the capture pipe open. Never raises; True only when npx exited 0. agent-browser is no longer a root package.json dependency (#43564) — it resolves lazily via ``npx agent-browser`` instead, which keeps it out of the npm workspace install graph entirely (nothing to prune it anymore) but means the first real invocation in a session would otherwise pay npx's registry-lookup/fetch cost. Calling this during ``hermes update`` (or ``hermes doctor --fix``) warms npx's own cache ahead of time, restoring the "available before any session starts" property agent-browser had while it was an eager root dependency — without re-entangling it with the workspace graph. FPATHr5T)stdoutstderrtextenvposix) creationflagsstart_new_sessionCREATE_NEW_PROCESS_GROUPrr--ignore-scriptsz--prefer-offline-yz --versionstdin)r|N)r*r^_build_browser_envr=get subprocessPIPErrUupdatergetattrAGENT_BROWSER_NPX_SPECPopenDEVNULLrx communicate returncode _lifecycle_kill_process_tree isinstanceTimeoutExpired contextlibsuppress)r|r.npx_binr popen_kwargscmdprocexcs r warm_agent_browser_npx_cachersz )C G  "C%cggfb&9:CK$.OOzX\ehiL ww'*<*>RVW(:(? ||x RWW\\$ 8_MN ||w ~.X"'',,tYPW2X RWW\\%9: Lr2rootcl tdtj|DS#t$rYywxYw)zxTrue when ``root`` holds a Playwright ``chromium-*`` / ``chromium_headless_shell-*`` dir (agent-browser accepts either).c3>K|]}|jdyw))z chromium-zchromium_headless_shell-N)r)res r r!z&_has_chromium_build..seq1<< IJesF)anyrr"r#)rs r _has_chromium_buildrs7eTVT^T^_cTdeee s $' 33ct}|j |jStjj ddj }t |xr6tjj|xstj|xs.tddDxstdtD|_|jS)a0True when a usable Chromium (or headless-shell) build is on disk; cached. Checks ``AGENT_BROWSER_EXECUTABLE_PATH``, then system Chrome/Chromium on PATH, then Playwright's cache. Without a binary the CLI hangs on first use until the command timeout fires, so the tool must not be advertised. AGENT_BROWSER_EXECUTABLE_PATHr5c3FK|]}tj|ywrD)r[r\)rrUs r r!z&_chromium_installed..sjdv||D!js!)z google-chromechromiumzchromium-browserchromec3|K|]4}|xr,tjj|xr t|6ywrD)rrrr)rrs r r!z&_chromium_installed..s0odtI d+I0CD0IIos:<) r*_cached_chromium_installedrrrrErvrisfiler[r\rr)r.ab_paths r _chromium_installedrs )C %%1---jjnnrsW  !<}}>*.69Q eCHo   Wd3iW6s6C6zszGGGpsptpYsYR3:R$R (3-  ES E-11#T1#S1#h)%)4)X S cd*T*$#!T#!LD !D !F '4 'r2