v0.4.0

The plugin no longer overrides any Hermes core tool or module (per the Hermes plugin catalog rules). Windows Spaces now run Hermes' own file tools over Git Bash; the plugin installs Git for Windows (and Python) in a Windows Space that lacks them, and stops with a clear error naming the fix if it cannot. The PowerShell file tools from 0.2.0 are gone. See #5.

0.3.0

• New sessions start in the Space's home folder (Hermes with default_cwd support).
• Bot Desktop, computer_use and the browser run inside Linux Spaces (Hermes with NousResearch/hermes-agent#142225, cua 0.7.0 or newer on PATH).
• New desktop setting installs the display stack into a Linux Space.
• Works with the cua Python package 0.5 to 0.7.

0.2.0: Windows Spaces

Hermes can now use a Windows Space. Before, the plugin refused one.

• The terminal tool runs in PowerShell (pwsh if the Space has it, else powershell.exe). Output is UTF-8, exit codes carry through, and sessions start in the user profile folder.
• Reading, writing and patching files work on Windows paths, and keep line endings and byte-order marks.
• File search, background processes and execute_code need Git for Windows in the Space. Without it they say what to install; nothing else is affected.
• Linux and macOS Spaces are unchanged.

Tested in CI on Linux, macOS and Windows (real Windows PowerShell and Git Bash). Not yet run against a real Cua Windows Space: Cua Cloud ended on 18 Oct and a local Windows Space needs QEMU. See the README's Windows Spaces section for the per-tool table.