Please don't hard code .claude profile anymore

[nateritter]

I realize this is a nitpick, but as a contractor with many different Claude profiles (like .claude-personal, .claude-contract1, .claude-work, et al), I had to take a day or two to make Claude dig through PAI and redo all the hard-coded .claude mentions.

Making this work in whatever profile or directory one would like it to be in would be helpful for future folks, but I imagine for me and others who use profiles when upgrades come around.

At the very least, not hard-coding .claude, but rather making it relative to the install path into upgrades would be nice.

[danielmiessler]

Hey @nateritter, 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.