danielmiessler
Fresh setup and nothing works
Followed the guide to install on linux, configured api keys and restarted shell. I open claude and get hit with:
⎿ SessionStart:startup hook error
⎿ SessionStart:startup hook error
⎿ SessionStart:startup hook error
Nothing seems customized and there are no skills because claude expects a lowercase skills dir and you have a Skills dir.
When I close Claude I get hit with another error:
SessionEnd hook [${PAI_DIR}/Hooks/capture-all-events.ts --event-type SessionEnd] failed: /bin/sh: 1: __HOME__/.claude/Hooks/capture-all-events.ts: not found
SessionEnd hook [${PAI_DIR}/Hooks/capture-session-summary.ts] failed: /bin/sh: 1: __HOME__/.claude/Hooks/capture-session-summary.ts: not found
I just watched your YouTube video with Clint and was excited to try this out. What am I doing wrong?
looks like a path issue. have you configured $PAI_DIR to point to your $HOME/.claude folder ?
It appears the issue is that the setup script will add the configuration to .claude/config/profile.json but not to .claude/settings.json
I also manually symlinked .claude/skills to .claude/Skills to fix that issue
Yes, that's what I alluded to above, but I don't understand why there is a claude/config/profile.json and also a claude/settings.json.
I experienced this same issue today on fresh install. I also discovered there seem to be two separate 'setup' scripts which seemingly do the same thing, but seems confusing and a bad practice.
Same issue here, were you finally able to fully fun PAI ? im on Windows btw, The hook works manually but fails at SessionStart. Root cause: settings.json uses Unix-style paths which don't work on Windows
I just used symlinks to the folders the pat is referencing but this is something that should be addressed in the future so its platform agnostic
I recommend oh-my-opencode instead of this repo: https://github.com/code-yeongyu/oh-my-opencode
PAI 2.0 Migration Notice
Thank you for reporting this! We've recently released PAI v2.0, which takes a fundamentally different approach from v1.x.
What changed: PAI v1.x tried to mirror the entire Kai system as an installable template. That approach created too many interconnected dependencies—change one piece, and others broke. v2.0 shifts to modular packs: self-contained, independently installable capabilities that work without understanding the whole system.
This issue: Because the architecture is now fundamentally different, we're closing all open v1.x PRs and issues. This isn't us dismissing your report—we appreciate it! The system has changed so significantly that we need to revisit concerns within the new context.
Next steps:
- Read the updated README (especially "The Journey: PAI v1.x → v2.0")
- Check out the new PAI Packs system
- If this issue still exists in 2.0, please open a new issue with context for the new architecture
We're absolutely happy to address these concerns—just within the 2.0 framework. Thanks for your patience! 🙏
