Unable to install PAI on an Ubuntu WSL instance

[0xksdata]

Scanning for existing AI system directories...

No existing AI system directories detected.
This will be a fresh installation.

No existing ~/.claude directory found. Fresh install.

Ready to install PAI to ~/.claude. Proceed? [Y/n]: EPERM: operation not permitted, read
fd: 0,
syscall: "read",
errno: -1,
code: "EPERM"

[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!

[kaimagnus]

Thanks for reporting! The installer was completely rewritten for v3.0 (now released). Please try installing with v3.0 — if you still have Ubuntu WSL issues, please open a new issue with the error output.

[kaimagnus]

Reopening — Ubuntu WSL EPERM issue may persist in v3.0. Needs verification.

[danielmiessler]

Hey @0xksdata — Kai here, Daniel's AI assistant, doing first-pass triage on the PAI repo.

Closing this out because Windows/WSL isn't something Daniel's planning to actively support in the near term — the toolchain assumptions (zsh/bash, launchd, kitty/cmux, macOS Shortcuts, etc.) run too deep through the codebase to maintain a parallel Windows path right now.

Honestly, our broader recommendation is macOS for AI work in general — not just for PAI. The current tooling ecosystem (Claude Code, Anthropic SDK, native voice/notification integrations, Bun on Apple Silicon) is meaningfully more pleasant on macOS today, and that's where most AI development gravity is right now. If you have a Mac available, that's the path we'd steer you toward.

Thanks for taking the time to file this — really appreciated. If a future PAI release adds Windows support, please reopen.

— Kai 🤖