I had to do a lot of changes to install and settings on setup for Windows

[cFors4]

Hey, I had to do a lot of changes to install and settings on setup for Windows. I'll open a PR shortly, but thought worth mentioning here

[Gerkinfeltser]

I'm watching with interest. I also had to do quite a bit, especially hook wise to get stuff working though I still had to make some compromises/forget some of the functionality.

Anyway, I look forward to seeing your PR/experiences!

[badosanjos]

I'm passing throw the same path. I'm using Windows with Cloud Code in VSCode and Claude Desktop. I need to some changes into the Kai Observatory Dashboard because the way that the code was built it do not works in Windows. And I'm doing some effort with Powershell to to have a personal and a "professional" Kai version living together, but to keep the learning and history with each instance. So I'm creating Claude Code versions with alternative names that call particular .claudes, and Powershell is giving some work. I really do know yet the best way to do this sharing of code into the Kai 2.0 to the Windows user, it should be a commit/branch ? A Windows Bundle ? A Fork ? If PAI 2.0 will support natively all systems it should be commit/branchs and the code be smart enought to detect and use the correct instruction. If Linux, Bash and Claude Code will bw the native pattern, it should be a windows bundle maybe.. appreciate to see your comments in that..

[badosanjos]

My observability server is working too.. but after several changes because the scripts were not running in Windows. Now I'm focusing in check the rest. And I don't know if the all the system is working when using the Claude Code VSCode Extension terminal to interact with PAI.

[badosanjos]

Do you use Claude in Windows in terminal or using any other IDE ?

[Gerkinfeltser]

I use vscode as well. I added in debug stuff to make sure the hooks were working as well. Again all seem to work on my end after having cc hack at them & lots of frustration. 😅

[badosanjos]

Well... PAI is working here in native Windows system, but it changed lot's of things in some Core packs, so definively will need a PR. But I was taking a look in some PRs already here with Packs suggestions, I believe that will be a nightmare, maybe we the Windows + VsCode users will need to be fixing and adding PRs for all the packs all the time. I was thinking about the advantages to instead of work with native Windows PRs and workarounds, will not be more effective standardize the usage of WSL and the setup of VsCode to use Claude Code Extension in WSL instead into the native Windows system. Will appreciate to listen your comments in this @cFors4 @Gerkinfeltser , what you thing about pros/cons if we propose to standardize WIndows users to use Vscode + Windows + WSL for Windows users ?

[Gerkinfeltser]

I started on full Windows as a PAI newcomer, but quickly got frustrated due to lack of (personal) knowledge and moved to WSL. That worked for a while, but stale disk cache issues caused persistent problems, so I moved back to full Windows and have been doing okay with it (though I've had to adapt some TypeScript to work better on Windows). I'm hoping to build a skill that helps packages work more easily for Windows users, though I've also moved over to OpenCode since I don't have the budget for Claude Max. :)

On the OpenCode side, hooks remain the main sticking point. I haven't had time to fix them yet. Honestly, most of PAI should work on Windows if you keep a few things in mind—specifically hooks and path handling in settings.json, which don't expand properly. You need to write them out explicitly with the correct slashes. Also, for the most part I just symlink a bunch of stuff into where it needs (~/.claude) and it works pretty well in both cc & oc.

[adgower]

can use with codex on windows?

[Nrconlon]

I'm having a really hard time figuring out the windows installation. Claude code got it sort of installed but I think there's still issues. I can't tell where the .claude directory is supposed to be. Some things indicate that it should be in C:\Users\User.claude, but it seems like its supposed to also be under PAI? The install put it in PAI\Bundles\Kai\undefined.claude, which is maybe what's intended but it's really hard to tell. The CreateSkill/SKILL.md file was looking for bun run $PAI_DIR/Tools/validate-pack.ts, but the validate-pack is in PAI.Tools. Maybe The entire PAI folder is supposed to be in .claude. I'm having a difficult time, any help would be appreciated. Super excited to get PAI up and running! Also excited for the discord

[Gerkinfeltser]

The global .claude is usually at C:/Users/User/.claude (aka ~/.claude for Linux/Mac users, though windows powershell should work as well with ~ notation). I personally have a separate dir I create folders like agents, commands, etc. & symlink back into the ~/.claude .

For the bun run stuff in the settings.json you'll need to replace those instances of $PAI_DIR with the full path where you have your PAI dir setup as windows doesn't seem to expand those json paths correctly. Also many/most of the bun .ts won't probably work out of the box and need further modifications to run effectively on windows unfortunately...

Also windows uses different slashes generally than Mac/linux but as cc uses bash, // or , either should work for paths in the settings.json. Confusing, I know. I can elaborate further as you need. It too much thrashing & experimenting for me to get it working.