core vs LifeOS
Self-hosted, always-on "personal AI OS": watches your apps, keeps a persistent memory graph, and acts autonomously within guardrails — a product, not a library for building agents. — versus — Daniel Miessler's LifeOS: an AI 'life operating system' that carries your goals and context into every task — an intent engineering platform with dashboard, agents and installer.
Both 'personal AI OS' plays: core is an always-on shipped product watching your apps with a memory graph; LifeOS is an open scaffold of intent, agents and commands you inhabit on top of Claude Code.
| core | LifeOS | |
|---|---|---|
| Stars | 2.0k | 19k |
| Forks | 189 | 2.4k |
| Language | TypeScript | TypeScript |
| License | NOASSERTION | MIT |
| Last activity | 13 days ago | 17 days ago |
| Topics | agents, memory | agents |
| Curated connections | 11 | 3 |
core — the curator's take
Reach for CORE when you want an event-driven, self-hosted personal assistant that notices things on its own, remembers across sessions via a memory graph, and acts across your apps with per-action approval gates. NOT the pick if you want a framework to embed agents inside your own software (it's a product/OS, not a toolkit), nor if you need to run a multi-agent team/company with org charts and budgets — that's paperclip's lane.
LifeOS — the curator's take
The most-starred personal-AI-OS scaffold: markdown, commands and agents on top of Claude Code, organized around TELOS (your goals) so every task starts from what you actually want. A philosophy with an installer — adopt the structure, not just the files. NOT a library; expect to live inside its conventions.