Native Windows support (PowerShell installer)#39
Merged
Conversation
…vices) Hermes runs natively on Windows (uv-based git clone at %LOCALAPPDATA%\hermes), so ghost can too. The one blocker -- the bash fork relocates the engine venv by rewriting paths, which can't work on Windows (Scripts\*.exe launchers bake the interpreter path into the binary) -- is solved by having the Windows fork RECREATE the venv with uv instead (uv venv + uv sync), the same way Hermes builds it. - install.ps1: PowerShell installer mirroring install.sh (self-bootstrap clone, uv, install Hermes if missing, fork+debrand, isolated privacy venv via uv sync, Task Scheduler services for scrubber + og-veil, ghost/.cmd command shims, PATH). - scripts/fork-engine.ps1: copy engine + recreate venv with uv + debrand.py + skills isolation + verify. - README: Windows PowerShell one-liner + platform badge. NOTE: authored without a Windows machine -- both .ps1 files are PowerShell-parse- checked but the install flow is UNVERIFIED on real Windows. Needs a Windows box to validate and debug. macOS/Linux install.sh is untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hermes runs natively on Windows (uv-based clone at
%LOCALAPPDATA%\hermes), so ghost can too.The blocker I flagged -- the bash fork relocates the engine venv via path-rewriting, which can't work on Windows (
Scripts\*.exelaunchers bake the interpreter path into the binary) -- is solved by having the Windows fork recreate the venv withuv(uv venv+uv sync), exactly how Hermes builds it on Windows.install.ps1mirrorsinstall.sh: self-bootstrap clone, uv, install Hermes if missing, fork+debrand, isolated privacy venv (uv syncof pyproject), Task Scheduler services for the scrubber + og-veil,ghost/ghost-login/ghost-update.cmdshims, PATH.scripts/fork-engine.ps1: copy engine + recreate venv with uv + debrand.py + skills isolation + verify..ps1files are PowerShell-parse-checked (no syntax errors), but the end-to-end install is unverified on real Windows -- it needs a Windows box to validate and almost certainly some debugging (venv recreate, Task Scheduler, paths). The macOS/Linuxinstall.shis untouched.