🚨 Renaming the Project from PAI to LifeOS (LifeOS 6.0.0)

[danielmiessler]

Hey all!

Some super exciting news to share. Two big things:

1. A big part of the evolution of PAI over the last few months, and couple releases, has been moving to more a Life and Work focus, as opposed to a pure Coding Harness function. We're making this refocus a whole lot more explicit and prominent now by renaming to LifeOS!
2. As part of this major change we're also changing the way LifeOS is distributed and updated. We're moving to distributing LifeOS as a Skill instead of a standalone .claude directory!

Project focus

So the focus will be much more whole-life-and-work focused going forward, centered specifically around the motion from Current State to Ideal State. We won't be removing any of the pure technical and coding benefits of the system, however. In fact, I've been running 6.0.0 for a while now and I've been shipping like a madman. What you'll expect to see in coming months on this front is more focus on PULSE, the LifeOS Dashboard, showing you more about your life, your TELOS, your work, your projects, and overall where you are vs. where you're going.

Distribution focus

The reasons for moving to a Skill-based distribution are too many to name, but here are some of the thoughts that went into the decision.

• Shipping a full .claude directory was nice in many ways, but it was quite fragile
• PAI was one of the first real Harness Engineering projects out there, so at the time we weren't really competing with people's existing installs. Now we all have our own customized harness on various different stacks, and each new PAI release was hard to integrate.
• Shipping as a Skill makes that much easier because all harnesses speak Skill as a language.
• The Skill will also include an install script and templates for the more system-wide, harness-affecting components of LIfeOS, including System Prompt, Hooks, etc.
• The new install is meant to be run inside your existing system, so your AI, using the installer, can look around at itself, see what's in the Skill, and have a conversation with you on what parts to take and what parts to leave.
• We also anticipate a much easier time keeping everything updated. Not guaranteeing perfection here, but what I'm looking to do is go more open-source-native with how updates are handled. Meaning, I am running and using the same LifeOS system that everyone else is, and when we merge something I'm using it as well, and vice versa. I do have concerns about how I'm going to do that safely, but I think it's going to be a whole lot easier as a Skill vs. my entire harness directory.

Majorly hyped about this change.

Expect to see a bunch of Issues and PRs and Discussions getting closed (like often happens around a release), but the reasoning should be even more obvious and transparent this time. A massive number of the outstanding issues have always been around the base harness, and by being more harness-agnostic we should bypass a ton of those issues.

Please accept my deep thanks for submitting issues, being vocal, and sharing all the great videos and write-ups about what you've done with PAI so far. Means a ton to me, and we're just getting started.

We're still in the punch card days of AI, and I'm thrilled to be in the Max Max buggy with you all.

(The actual 6.0.0 release is imminent, probably within 24 hours)

[stephtara]

I'm looking forward to seeing this!
Two things I'm wondering about at this stage:

• does make it "skill-based" mean it will be more easy to use "what I think of as PAI" to a different model than Claude?
• what are the implications for those of us (or at least me) who have never used Claude Code outside of PAI?

[danielmiessler]

It should be far easier to install and implement on any system, including Claude Code, which is still my main driver.

[CaptainCodeAU]

I am looking forward to migrating from v4 to v6.

[jaylarr176]

Super pumped for this, thank you for all your hard work!