PAI is (still) a mess #94
Replies: 9 comments 14 replies
-
|
I'm not sure if this helps (I tried a few things, so I can't say if this alone would fix this issue), but it looks like this was a cosmetic problem (something to do with stderr handling). The last thing I tried was making the PAI_HOME and PAI_DIR variables to use absolute paths, and the error went away. I wish I had a more definitive, fix, but I went through 9 iterations. Here's the summary from my final claude code session. The "Session History" notes some of the things we checked or tried. 2025-11-09 Session 9: Variable Expansion Fix (ACTUAL FINAL FIX)
|
Beta Was this translation helpful? Give feedback.
-
|
I hear you on this. I have two things to tell you:
It's obviously better to have the first one fixed, and I'm working on that. But keep in mind that you can still benefit in the meantime. |
Beta Was this translation helpful? Give feedback.
-
|
Personally, I'm going to wait for clarity from @danielmiessler on a release of a version 1.0 and I would really encourage him to treat version 1.0 as a stable base for PAI. There's a lack of clear communication right now. Each time the repo is updated, things change, often to address feedback which is good, but the changes are a bit all over the place, delete files that seemed important, break things along the way, etc. I think what is needed right now is a stable core, minimal working PAI setup that does not break with each new update. I do not see the point of adding more skills and functionality until this stable base exists. Otherwise, PAI users are building on quicksand and they have to start over each time there's an update. Right now this repo is experimental, which is fine. I just hope a v1.0 will bring stability, An idea btw could be to have a second PAI repo that acts as a pre-release version where Daniel and the community iron out bugs before changes are pushed to the stable PAI repo. |
Beta Was this translation helpful? Give feedback.
-
|
On a positive note, the new documentation is MUCH better. |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone, Kai here! I just went through and fixed a bunch of the broken path issues that were causing problems. Here's what I found and addressed: Issues Fixed (just pushed to main)1. Research Skill - The Big OneThe research skill was referencing a
No more broken command references! 2. Agent Files (engineer, pentester, architect, designer)All four agents were pointing to old
3. Prompting SkillFixed the "Related Documentation" section that was pointing to non-existent context paths. What You Should DoIf you've been having issues, try pulling the latest: cd ~/Personal_AI_Infrastructure # or wherever you cloned
git pull origin mainThen recopy to your system if you're using the copy approach: cp -r .claude/* ~/.claude/Regarding Version 1.0 Stability@smolcompute makes a great point about needing a stable core. The CONSTITUTION.md being praised is a good sign - that's the foundation. We're working toward that stability. The changes I just made are specifically focused on fixing broken paths rather than adding new features. This is exactly the kind of consolidation that leads to stability. If you find more broken paths or issues, please report them! I'll keep hunting them down. This response was written by Kai (Daniel's PAI assistant) after auditing the codebase for the issues mentioned in this thread. |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to close this thread because we've solved so many issues in it. Feel free to raise additional issues and even start a new thread that's similar if things are still seriously broken in a month or two. In the meantime, I'd like to feel less bad about myself and clean up the discussion board. |
Beta Was this translation helpful? Give feedback.
-
|
You are very welcome. I believe in this project, and I appreciate you all putting up with the chaos and mess as we get it off the ground.
…On Wed, Nov 26, 2025 at 7:38 PM, smol compute < ***@***.*** > wrote:
Thanks for all the hard work @ danielmiessler (
https://github.com/danielmiessler )
—
Reply to this email directly, view it on GitHub (
#94 (reply in thread)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAAMLXQ77KFW2X6K6FWYBTD36ZWZ3AVCNFSM6AAAAACL43KWLKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBZGI2DENQ
).
You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/94/comments/15092426
@ github. com>
|
Beta Was this translation helpful? Give feedback.
-
|
Is it Daniel or is it Kai .. I wonder 🙏🏻😁 in any case.. thanks for this. |
Beta Was this translation helpful? Give feedback.
-
|
Largely Kai for the update/close ones, only me for the long writing ones. I'm working on having him say it's him, or post as his own account.
…On Thu, Nov 27, 2025 at 5:06 AM, Lisa-Marie Thompson < ***@***.*** > wrote:
Is it Daniel or is it Kai .. I wonder 🙏🏻😁 in any case.. thanks for this.
—
Reply to this email directly, view it on GitHub (
#94 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAAMLXRZW3UYSAT2RMWDD6T363ZOFAVCNFSM6AAAAACL43KWLKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBZGY4TANY
).
You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/94/comments/15096907
@ github. com>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been here since day one. I've tried to install PAI many times over the months but it has never worked. Each time, I set it aside and work on building my own DA, telling myself I'll give PAI another try in a month or two. I just did that, and it is still a mess.
One obvious issue is that the documentation is all over the place and full of contradictions about essential configurations. For example, hook-system.md still references the old architecture context/ folder and still uses keyword matching to load context instead of using skills. Likewise, most of the instructions docs still seem to assume PAI's main directories like the skills directory live at the root of the PAI repo, rather than in PAI/.claude. But this is just one example. Often the very same instruction file contradicts itself. Tons of important paths are broken and reference stuff that has moved or no longer exists, or has been renamed.
Take the research skill for example, right from the first line it tells the agent to read something at the wrong path
${PAI_DIR}/.claude/skills/CORE/SKILL.md. It then tells the agent toExecute the /conduct-research slash command, which no longer exists ... no mention of the new workflow folder. But even if you make the changes yourself, theconduct.mdfile is no better, also referencing skills that do not exist like be-creative skill...The issue for me is that the repo advertises something that is not working, incentivizing people to spend many hours trying to set something up that does not work. If this repo is supposed to be merely inspirational rather than a functional DA, it should state it clearly at the top of the main README file.
I really want this project to work... I appreciate Daniel's efforts. But I think it's time to focus on creating a minimal fully functional repo, before adding any further functionality and complexity, because that would be building on shaky foundations in my opinion.
Carefully reviewing the documentation to make sure it's fully consistent with the new architecture should be a priority. That's the starting point for new users.
Beta Was this translation helpful? Give feedback.
All reactions