RedPlanetHQ

core

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.

★ 1,877⑂ 175● TypeScript⚖ NOASSERTIONupdated today

agents orchestration

View on GitHub

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.

Mapped by ShipWithAI editors · links verified

README.md

Curator's take

🌐 Language

Your Personal AI OS

Not a chatbot you open. An AI that is always on, always watching. Name it. Shape it. Connect it to everything you use. Reach it however you work. Open source, self-hosted, yours forever.

See it work

Watch CORE take a plain-text task, gather context from GitHub and memory, plan the work, run a Claude Code session, and open a PR:

Always watching. Always rea

Continue your stack

What teams reach for next — and why each earns a place beside core.

Alternative to

paperclip

Open-source control plane for running fleets of heterogeneous AI agents as a "company" — bring your own agent, assign goals, org charts, budgets, governance, and an audited ticket system.

Why it fitsBoth are the layer ABOVE agent frameworks rather than a framework themselves, and both spawn coding-agent sessions — but CORE is a personal, memory-driven, always-on assistant while paperclip manages fleets of agents as a team/company. Pick CORE for a personal AI OS, paperclip for multi-agent org governance.