Issue installing PAI 5.0 on WSL

[lrauhockey]

Installation starts, the installation UI starts and walks me thru it.

In the background you see the following.
[154693:0512/204912.400608:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

Then after the install i get the following

ℹ Launching pai...
zsh:1: command not found: pai

a find, wont even find it.

Running WSL Ubuntu - on win11

[JimmayVV]

Sadly this is something Daniel decisively is choosing not to support.

Combine this with the hard reliance on Claude Code, and I've been looking for ways to migrate the architecture principles here to new harnesses (exploring Local LLM's too).

See issue #1117

I suggest that Daniel add a supported platforms/services notation high up in the README for clarification.

I previously got v4.0.3 working quite well in WSL2 - I even substituted the ElevenLabs API with a self-hosted Text To Speech platform which is working great. I was sad to see that issue

[5bxn]

Sadly this is something Daniel decisively is choosing not to support.

Combine this with the hard reliance on Claude Code, and I've been looking for ways to migrate the architecture principles here to new harnesses (exploring Local LLM's too).

See issue #1117

I suggest that Daniel add a supported platforms/services notation high up in the README for clarification.

I previously got v4.0.3 working quite well in WSL2 - I even substituted the ElevenLabs API with a self-hosted Text To Speech platform which is working great. I was sad to see that issue

I installed 5.0 on an ubuntu vps the day after release and that took a while to get going, but the wsl2 install at my work laptop the other day was not terrible. NOTE; in retro I think there was a bun install there somewhere too.

$ uname -r
6.6.114.1-microsoft-standard-WSL2
$ head -7 /etc/os-release
NAME="AlmaLinux"
VERSION="9.7 (Moss Jungle Cat)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.7"
PLATFORM_ID="platform:el9"
PRETTY_NAME="AlmaLinux 9.7 (Moss Jungle Cat)"
 
git clone https://github.com/danielmiessler/Personal_AI_Infrastructure.git
cd Personal_AI_Infrastructure/
vi README.md
cd Releases/v5.0.0/
cp -R ~/.claude ~/.claude.backup-$(date +%Y%m%d)

bash ./install.sh
sudo dnf install nss.x86_64
bash ./install.sh
sudo dnf install   atk   at-spi2-atk   gtk3   libXcomposite   libXdamage   libXrandr   libXScrnSaver   alsa-lib   nss   cups-libs
bash ./install.sh
claude

and with openrouter config in .bashrc I don't need any expensive models either
$ tail -10 ~/.bashrc
export OPENROUTER_API_KEY="sk-or-v1-268923d35b638blablabla..."
export ANTHROPIC_BASE_URL="https://openrouter.ai/api"
export ANTHROPIC_AUTH_TOKEN="$OPENROUTER_API_KEY"
export ANTHROPIC_API_KEY="" # Important: Must be explicitly empty

export ANTHROPIC_DEFAULT_OPUS_MODEL="nvidia/nemotron-3-super-120b-a12b:free"
export ANTHROPIC_DEFAULT_SONNET_MODEL="nvidia/nemotron-3-super-120b-a12b:free"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="nvidia/nemotron-3-nano-30b-a3b:free"
#export CLAUDE_CODE_SUBAGENT_MODEL="openrouter/google/gemma-4-31b-it:free"
export CLAUDE_CODE_SUBAGENT_MODEL="nvidia/nemotron-3-super-120b-a12b:free"

[Seikilos]

Same here. Wonder how this works on Mac actually. The issue is that there is casing chaos in the code.

where pai
pai: aliased to bun /home/me/.claude/PAI/Tools/pai.ts

but

find . -name "pai.ts"
./PAI/TOOLS/pai.ts

So at least on my ubuntu box with prior 4.x installation the path is not correct due to casing.
When I do a

❯  grep -R "Tools" 2>/dev/null | wc -l
533
❯ grep -R "TOOLS" 2>/dev/null | wc -l
309

I get references to TOOLS/ and Tools, which is bad. I dont know how claude handles casing but as soon as some typescript will call such paths, they will always fail.

So this will probably require a lot of replacing and fixing before it will work reliably.

Edit: I've reviewed the code and it would require replacing a lot of paths to harmonize this.

Or ... just symlink and solve this dirty:

ln -s ~/.claude/PAI/TOOLS ~/.claude/PAI/Tools    

(And no, this was not vibe coded, I came with this dirty solution all by myself 😅)

Edit 2: Pulse also needs this (and probably much more fixing on linux to make it work)

[danielmiessler]

Hey @lrauhockey, thanks for raising this, and sorry it sat for a while.

We're changing how LifeOS ships. Instead of cloning a full ~/.claude directory and running it as a complete system, LifeOS is becoming a skill you install through an agentic installer. The installer hands integration to your own AI, which reads your actual machine (your OS, your paths, your harness) and wires the hooks and system prompt in where they belong.

That's aimed right at what you hit here. The old "one directory, one layout, hope it matches your setup" approach is exactly what broke for so many people, and the new model should handle it far better because your AI does the integration per machine instead of us guessing.

So we're closing this in prep for that release. If it still bites you once the skill-based version is out, reopen or file a fresh one and we'll jump on it. Appreciate you taking the time.