Run on Windows without recoding bits and pieces?

[mektigh]

Hi,

I really love this project and it runs flawless on my Mac.
But i would like to run it on my Windows Computer aswell.
Though the scripts is written exclusively to work on MacOS and wonder if anyone has found a good way to be able to update PAI when changes are made and still be able to run on Windows OS.

[danielmiessler]

Thanks for this feedback! We're currently working on PAI v3.0, which includes significant architectural changes. We're evaluating this issue in the context of the new architecture and will provide an update once v3.0 is closer to release.

Please stand by — we haven't forgotten about this and appreciate your contribution to making PAI better!

[mektigh]

Nice to hear, tell me if i can help in some way with testing etc! Much love for the work you put into this Daniel!

[chrisglick]

I was able to ask my PAI to upgrade itself to work on Windows. I'm going through the 2.5 -> 3.0 process now and I'll commit the fixes for a working Windows PAI.

[chrisglick]

@mektigh — Taking you up on that testing offer! 🙌

I've been running PAI 2.5 on Windows and recently updated to 3.0 after the release. I've got 3 PRs up that fix Windows compatibility across the board:

Recommended merge/test order:

1. feat: Add Windows compatibility guide and installer support #704 — Installer Windows support + compatibility guide (clean, no overlap with others)
2. fix: Cross-platform hook compatibility for Windows #706 — Runtime path fixes (HOME fallback, tilde expansion, cross-platform utilities)
3. fix: Replace Bun.stdin with process.stdin in 10 v3.0 hooks (Windows/MSYS) #713 — Bun.stdin → process.stdin migration + shared stdin utility + security hardening

If you want to test, the easiest way is to check out the fix/bun-stdin-windows-compat branch from #713 (it's rebased on latest main) and run PAI on Windows. The main things to verify:

• Hooks fire without hanging or crashing
• Session start/end works cleanly
• No Bun.stdin errors in stderr

Any feedback, like "it worked" or "it broke on X" is be super helpful.

Appreciate you volunteering! Windows support has been a gap for a while and more eyes on it would be great.

[m-slivinsky]

@chrisglick - have there been any further updates to getting PAI to work on windows? first time PAI user and I've only access to a windows machine, would love to know how to get the latest version (PAI 4.0.3) working on windows (or if only prior versions work that would be helpful too). let me know if there's anything I can test or otherwise do to support this effort.

Thank you!!

[danielmiessler]

I don't really recommend PAI on Windows. I recommend switching to macOS or Linux. I don't just say this because of PAI, but just in general pretty much all AI stuff is designed for a UNIX-based system, and you'll be at a disadvantage for the next few years if you're not on one. We're going to try to do what we can for Windows users, but it's not going to be as high a priority as some other core features.

…

On Thu, Mar 12, 2026 at 10:53 AM, m-slivinsky < ***@***.*** > wrote: *m-slivinsky* left a comment (danielmiessler/ Personal_AI_Infrastructure#543) ( #543 (comment) ) @ chrisglick ( https://github.com/chrisglick ) - have there been any further updates to getting PAI to work on windows? first time PAI user and I've only access to a windows machine, would love to know how to get the latest version (PAI 4.0.3) working on windows (or if only prior versions work that would be helpful too). let me know if there's anything I can test or otherwise do to support this effort. Thank you!! — Reply to this email directly, view it on GitHub ( #543 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAMLXXRIPWJ6FYG6PEWND34QL2RNAVCNFSM6AAAAACTREU4FKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANBYG43TSNRRHE ). You are receiving this because you commented. Message ID: <danielmiessler/Personal_AI_Infrastructure/issues/543/4048779619 @ github. com>

[LioChanDaYo]

I've been running PAI on Windows using WSL for two weeks now, and I've got to say I'm pretty satisfied. I don't think I'm missing out on functionalities except voice.

[chrisglick]

Hey @m-slivinsky — yes, there's been a lot of progress! I've been working on native Windows support (no WSL required) and just pushed the latest round of fixes today.

Here's how to get PAI 4.0.3 running on Windows right now:

Prerequisites: Install Git for Windows, Bun (PowerShell: irm bun.sh/install.ps1 | iex), and Claude Code (npm install -g @anthropic-ai/claude-code).

Install (in Git Bash):

git clone https://github.com/chrisglick/Personal_AI_Infrastructure_Windows.git
cd Personal_AI_Infrastructure_Windows/Releases/v4.0.3
cp -r .claude ~/ && cd ~/.claude && bash install.sh

If you already have Claude Code running, you can also tell Claude to install it for you — there's a non-interactive install guide at Releases/v4.0.3/.claude/INSTALL_GUIDE_FOR_CLAUDE.md in the repo that Claude can follow step-by-step.

What's been fixed so far:

• Platform abstraction layer (lib/platform.ts) for cross-platform path/process handling
• All hooks patched: Bun.stdin → process.stdin, HOME → USERPROFILE fallback, bun prefix for Windows shell execution
• Installer engine fixes for Windows (temp dirs, process spawning, symlink fallbacks)
• Banner and CLI tools work in Windows Terminal / Git Bash
• settings.json hook commands all work through Claude Code's bash shell

What's still experimental:

• Voice server auto-start (works manually, no LaunchAgent equivalent yet)
• The interactive installer may hang if driven by Claude Code (use the non-interactive guide instead)

The fork is at chrisglick/Personal_AI_Infrastructure_Windows. Would love help testing — if you run into issues, open an issue on the fork and I'll get to it quickly.

As @danielmiessler noted, macOS/Linux is the primary target, but the core PAI experience (skills, hooks, memory, the Algorithm) works on Windows. @LioChanDaYo's WSL approach is also solid if you'd rather go that route.

[m-slivinsky]

@chrisglick this is tremendous - thank you so much!!

[mektigh]

I don't really recommend PAI on Windows. I recommend switching to macOS or Linux.

I don't just say this because of PAI, but just in general pretty much all AI stuff is designed for a UNIX-based system, and you'll be at a disadvantage for the next few years if you're not on one.

We're going to try to do what we can for Windows users, but it's not going to be as high a priority as some other core features.
…

I use Mac for nearly everything, but when i game and stuff i would love to have PAI by my side so its fine not being a priority.

@chrisglick
Sorry for not getting back to ya, been away and got limited time, i will test your latest version this weekend i think :)

As for the WSL, it works with minor missing pieces such as voiceserver and that stuff, wich i look forward to see more off so that we in the future can have a flowing conversation with pai :)

[pixelloop]

Hey @m-slivinsky — yes, there's been a lot of progress! I've been working on native Windows support (no WSL required) and just pushed the latest round of fixes today.

Here's how to get PAI 4.0.3 running on Windows right now:

Prerequisites: Install Git for Windows, Bun (PowerShell: irm bun.sh/install.ps1 | iex), and Claude Code (npm install -g @anthropic-ai/claude-code).

Install (in Git Bash):

git clone https://github.com/chrisglick/Personal_AI_Infrastructure_Windows.git
cd Personal_AI_Infrastructure_Windows/Releases/v4.0.3
cp -r .claude ~/ && cd ~/.claude && bash install.sh
If you already have Claude Code running, you can also tell Claude to install it for you — there's a non-interactive install guide at Releases/v4.0.3/.claude/INSTALL_GUIDE_FOR_CLAUDE.md in the repo that Claude can follow step-by-step.

What's been fixed so far:

• Platform abstraction layer (lib/platform.ts) for cross-platform path/process handling
• All hooks patched: Bun.stdin → process.stdin, HOME → USERPROFILE fallback, bun prefix for Windows shell execution
• Installer engine fixes for Windows (temp dirs, process spawning, symlink fallbacks)
• Banner and CLI tools work in Windows Terminal / Git Bash
• settings.json hook commands all work through Claude Code's bash shell

What's still experimental:

• Voice server auto-start (works manually, no LaunchAgent equivalent yet)
• The interactive installer may hang if driven by Claude Code (use the non-interactive guide instead)

The fork is at chrisglick/Personal_AI_Infrastructure_Windows. Would love help testing — if you run into issues, open an issue on the fork and I'll get to it quickly.

As @danielmiessler noted, macOS/Linux is the primary target, but the core PAI experience (skills, hooks, memory, the Algorithm) works on Windows. @LioChanDaYo's WSL approach is also solid if you'd rather go that route.

Is there a way to move an existing WSL install to Windows? or would you have to start afresh? With the new Claude Desktop updates and CLI plugins working in the Desktop version of Claude Code, I would love to see if I can get that working. Or maybe it would be smarter to see if there's eventually a Claude Desktop plugin version of PAI and then migrate all files.