pro-workflowOne SQLite store under every Claude Code session: corrections become FTS5-searchable rules that auto-load, research grows persistent wikis, and 37 hook scripts add quality gates.
Why switchSame core job — corrections that stick across Claude Code sessions. claude-reflect is the focused plugin (corrections → CLAUDE.md); pro-workflow builds a whole SQLite-backed memory-and-hooks platform around the idea.
Full comparison → ECCCross-harness 'operating system' for coding agents — 268 skills, 66 agents, hooks, rules, memory persistence, instinct-based continuous learning and AgentShield security scanning. MIT.
Why switchBoth close the learning loop from your corrections: claude-reflect is a focused Claude Code plugin syncing approved learnings to CLAUDE.md; ECC's instinct system does the same continuous-learning job with confidence scoring inside a much larger harness framework.
Full comparison → SkillXResearch framework that auto-distills agent trajectories into a three-level skill knowledge base (planning, functional, atomic) — pluggable into weaker agents and new environments.
Why switchBoth turn agent experience into reusable knowledge: claude-reflect captures your corrections into CLAUDE.md pragmatically, SkillX distills full trajectories into a transferable skill hierarchy — research-grade.
Full comparison → coreSelf-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.
Why switchBoth 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.
Full comparison → opencode-memOpenCode plugin giving coding agents persistent cross-session memory — local SQLite + vector search, automatic memory capture, user-profile learning, and a web UI. Nothing leaves your machine.
Why switchBoth close the cross-session learning loop for coding agents: claude-reflect distills your corrections into CLAUDE.md via /reflect; opencode-mem auto-captures work into a searchable vector store and injects relevant memories per session.
Full comparison →