Choose theme
AI Resources
LifeOS
LifeOS adds personal context, memory, skills, work records and a local dashboard around an existing AI coding assistant.
Daniel Miessler's project stores goals and preferences in a USER tree and connects that context to repeatable workflows. Claude Code is its most-tested integration. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Personal context across sessions
A USER tree holds goals, preferences and current state instead of keeping that context only in a chat.
Why it stands out
Memory and reusable workflows
Skills and work records sit alongside the personal context and Pulse dashboard.
Availability
Repository and guided installation
The official installer detects Windows, macOS or Linux and the assistant configuration before proposing changes.
Why it matters
What makes it useful
If you return to a business or creative project in a fresh session, LifeOS gives the assistant stored goals, preferences and previous work to start from. The project materials remain in inspectable files rather than only in the conversation.
What to know
Where it fits
LifeOS supplies the context and operating layer; an existing coding harness provides model access and file or terminal tools. Connected browser, voice and cloud features have their own dependencies.
Notable points
What stands out
The install guide distinguishes context loading from always-on hooks. Claude Code has the hook integration; Codex, Cursor, Cline and Gemini can load the context and run requested workflows, but those hooks are not automatically wired there.
Before using
What to review
The installer adds the skill and runtime, scaffolds a USER tree and proposes harness integration and a launch command. Review the conflict scan and those configuration changes; back up the existing setup before upgrades.
Installer tools default to a dry run. The install guide says omitting --apply can report success while copying no files, so reading a successful plan and confirming an installed setup are separate checks.
Decide which personal context belongs in USER—especially work, health, finances or relationships—and which models or connected services may receive it. Local files do not make every model or service local; keep credentials out of material supplied as conversational context.
Check the documented launch command and dependency checks before relying on a feature being active.
Reader fit
Who may find it relevant
People already using a coding assistant who want their goals and work context available across sessions.
Builders willing to maintain files, integrations and backups; chat-only assistants without file and command access cannot install it.
Editorial note
Why LifeHubber lists it
LifeOS is interesting when remembering the project is only half the problem: you also want the assistant to follow the same working method next time. Its skills and routing sit alongside persistent context, so recurring research or writing can have a named workflow as well as remembered goals. That makes it a fuller starting point than saving a biography for the assistant, although the hooks and launch setup determine which parts actually run.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Keep the personal layer recoverable.
A system can remember more about you and still need an exit plan. These next steps help keep the important files, decisions, and fallback path visible outside one assistant setup.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
Paperclip
paperclipai/paperclip
A self-hosted server and dashboard for coordinating agent teams through companies, goals, roles, issues, heartbeats, budgets, approvals, and persistent activity records.
Genex Desktop
genex-games/genex-desktop
An early desktop workspace for making browser games with AI, combining game chat, playable previews, build history, assets, configurable model roles, local Blender tools, and static web export.
UX/UI Agent Skills
plugin87/ux-ui-agent-skills
A Claude-focused project kit that connects design tokens, component specifications, accessibility guidance, visual-taste references, UX writing, framework adapters, runnable skills, validation gates, rendered critique, and a product starter.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
