claude-reflect vs core
Claude Code plugin that learns from your corrections — hooks capture them in-session, /reflect syncs approved learnings to CLAUDE.md/AGENTS.md, /reflect-skills mines history into reusable commands. — versus — 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.
Both chase memory that compounds: core builds a full personal-AI OS with a persistent memory graph; claude-reflect does one narrow slice — your coding agent's lessons — with zero infrastructure.
| claude-reflect | core | |
|---|---|---|
| Stars | 1.3k | 1.9k |
| Forks | 109 | 181 |
| Language | Python | TypeScript |
| License | MIT | NOASSERTION |
| Last activity | 4 months ago | yesterday |
| Topics | coding, memory | agents, memory |
| Curated connections | 9 | 6 |
claude-reflect — the curator's take
Install claude-reflect the third time you catch yourself typing the same correction into Claude Code. It's the pragmatic take on agent memory: no vector DB, no service — hooks queue corrections, you review, markdown files get smarter, and the AGENTS.md sync means Codex/Cursor/Aider benefit too. The /reflect-skills pattern-mining is the sleeper feature: 15 similar requests become one command. When NOT: if you expect actual memory infrastructure (semantic recall, knowledge graphs) — this is disciplined note-taking with AI triage, personal-scale by design. Everything lands via human review, which is a feature, not friction.
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.