+ lHj Rt^RIHtHt^RIHt^RIHtRRRlltRRR R R R R R///t ]P!RR] RRR7R#)a3Read which OS window sits directly underneath the Hermes desktop window. The window list lives with the OS, so this round-trips through the gateway's blocking-prompt bridge like `read_terminal`: ``window.read.request`` -> the renderer's main process (native window enumeration) -> ``window.read.respond``. )CallableOptional read_pane)registryNcFV^8dQhR\\,R\/#)callbackreturn)rrstr)formats";/home/ubuntu/.hermes/hermes-agent/tools/read_window_tool.py __annotate__rsXh%73c\VRR4#)z@Return the window underneath the Hermes window as a JSON string.)z>read_window_below is only available in the Hermes desktop app.z!Failed to read the window below: zCould not determine the window underneath (the desktop app did not answer, or window enumeration is unavailable on this system).rr s&r read_window_below_toolrs Xr$ rnameread_window_below descriptionu|Identify the app window directly behind the Hermes desktop window (what the user is working in). JSON: {window: {app, title, bounds, id}, frontmost, platform}. title may be empty when the OS withholds it (noted in `note`); where windows cannot be enumerated at all, {error, platform} says what would fix it — relay that instead of retrying. Metadata only; never captures pixels. parameterstypeobject properties desktop_uic 8\VPR4R7#)r r)rget)argskws&,r r!.s5rvvj?QRru🪟)rtoolsetschemahandleremoji)N) __doc__typingrrtools.read_terminal_toolrtools.registryrrREAD_WINDOW_BELOW_SCHEMAregisterrrr r,sd&.#  :,      # R  r