Bj*hdZddlmZddlZddlZddgZdaddZddZd d d dd Z dd Z ddZ ddZ y)uWindows-safe stdio configuration. On Windows, Python's ``sys.stdout``/``sys.stderr`` default to the console's active code page (often ``cp1252``, sometimes ``cp437``, occasionally ``cp932`` on Japanese locales, etc.). Hermes's banners, tool output feed, and slash command listings all contain Unicode: box-drawing characters (``─┌┐└┘├┤``), mathematical and geometric symbols (``◆ ◇ ◎ ▣ ⚔ ⚖ →``), and user-supplied text in any language. Printing those to a cp1252 console raises ``UnicodeEncodeError: 'charmap' codec can't encode character…`` and kills the whole CLI before the REPL even opens. The fix is to force UTF-8 on the Python side and also flip the console's code page to UTF-8 (65001). Both matter: Python-level only helps when Python's stdout is a real TTY; code-page flipping lets subprocesses and child Python ``print()`` calls agree on encoding. This module is a no-op on every non-Windows platform, and idempotent. Entry points (``cli.py`` ``main``, ``hermes_cli/main.py`` CLI dispatch, ``gateway/run.py`` startup) call :func:`configure_windows_stdio` exactly once early in startup. Patterns cribbed from Claude Code (``src/utils/platform.ts``), OpenCode (``packages/opencode/src/pty/index.ts`` env injection), and OpenAI Codex (``codex-rs/core/src/unified_exec/process_manager.rs``). None of those actually flip the console code page — they rely on their runtime (Node or Rust) writing UTF-16 to the Win32 console API and letting the terminal sort it out. Python doesn't get that luxury. ) annotationsNconfigure_windows_stdio is_windowsFc(tjdk(S)z4Return True iff running on native Windows (not WSL).win32)sysplatform5/home/ubuntu/.hermes/hermes-agent/hermes_cli/stdio.pyrr)s <<7 ""r c ddl}|jj}|jd|j dy#t $rYywxYw)usSet the attached console's input and output code pages to UTF-8. Uses ``SetConsoleCP`` / ``SetConsoleOutputCP`` via ``ctypes``. Failure is silent — if there's no attached console (e.g. Hermes is running behind a redirected stdout, under a service, or inside a PTY-less CI runner) these calls simply return 0 and we move on. CP_UTF8 is 65001. rNi)ctypeswindllkernel32 SetConsoleCPSetConsoleOutputCP Exception)rrs r _flip_console_code_page_to_utf8r.sI  ==))e$##E*    s1yesTruetruePYTHONIOENCODINGr PYTHONUTF8r!EDITORVISUAL) _CONFIGUREDrosenvironget setdefault_default_windows_editor_augment_path_with_known_toolsrrrstdoutstderrstdin)_default_editors r rrUs  <  zz~~348TT  JJ,g6JJ,,./Orzz~~h7 x@X. 8#$$% # # "K r c0ddl}|jdryy)uReturn a Windows-appropriate default for ``$EDITOR``. Priority order, first match wins: 1. ``notepad`` — ships with every Windows install, no deps, works as a blocking editor (``subprocess.call(["notepad", file])`` blocks until the user closes the window). This is the "always-works" default. The prompt_toolkit buffer's ``open_in_editor`` and Hermes's ``hermes config edit`` both honour ``$EDITOR``. Users who prefer a different editor can override: - VSCode: ``$env:EDITOR = "code --wait"`` (``--wait`` is critical; without it the editor returns immediately and any input is lost) - Notepad++: ``$env:EDITOR = "'C:\Program Files\Notepad++\notepad++.exe' -multiInst -nosession"`` - Neovim: ``$env:EDITOR = "nvim"`` (if installed) Set this before launching Hermes (User env var in Windows Settings, or export in a PowerShell profile) and Hermes picks it up automatically. rNnotepad)shutilwhich)r7s r r.r.s* ||I r c tsyddl}tjj dd}|sytj j |dddtj j |dddtj j |ddd dtj j |dd d d tj j |d ddg}tjj dd}|jtjDchc]}|s|j}}g}|D]F}tj j|s#|j|vs6|j|H|r5tjj g||tjd<yycc}w)uSPrepend well-known Hermes-managed tool directories to os.environ['PATH']. Fixes the "User PATH was just updated but my process can't see it" gap on Windows. When install.ps1 runs, it adds entries like ``%LOCALAPPDATA%\hermes\git\bin`` to the User PATH via ``SetEnvironmentVariable(..., "User")``. That write propagates to newly *spawned* processes only — already-running shells (including the one the user invokes ``hermes`` from right after install) retain their old PATH. Any subprocess Hermes spawns — bash, ``rg``, ``grep``, ``npm`` — inherits that stale PATH and reports commands as missing even though they're on disk. Symptom: ``search_files`` reports "rg/find not available" when the user clearly just installed ripgrep. Patch-up strategy: add the known Hermes-managed tool directories to our PATH at startup so subprocess calls resolve correctly. No-op on POSIX and when the directories don't exist. The User PATH broadcast still happens in the background for future shells; this just smooths over the first-launch gap. Nr LOCALAPPDATAr6hermesgitcmdbinusrz hermes-agentvenvScripts MicrosoftWinGetLinksPATH) rr7r*r+r,pathjoinsplitpathseplowerisdirappend)_shutil local_appdatacandidate_dirsexistingpexisting_lowerprependds r r/r/sY* <JJNN>26M   ]HeU;  ]HeU;  ]HeUEB  ]HnfiP  ]K7C Nzz~~fb)H)1 )CIAqaggiINIG  77==   ? NN1 ZZ__-Aw-A-AB 6 Js F>%F>)returnbool)rUNone)rstrrrXrUrW)rUrX) __doc__ __future__rr*r__all__r)rrrrr.r/r r r r\sO:# $l 3 #  .4;)  IXD9Cr