ECC vs pro-workflow
Cross-harness 'operating system' for coding agents — 268 skills, 66 agents, hooks, rules, memory persistence, instinct-based continuous learning and AgentShield security scanning. MIT. — versus — One 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.
Same job — a persistent operating layer under coding-agent sessions with hooks, learned rules and quality gates. pro-workflow is one SQLite store focused on Claude Code; ECC is the maximalist cross-harness system spanning 7+ harnesses with skills, agents and security tooling.
| ECC | pro-workflow | |
|---|---|---|
| Stars | 230k | 2.6k |
| Forks | 35k | 253 |
| Language | JavaScript | JavaScript |
| License | MIT | — |
| Last activity | 3 days ago | 4 days ago |
| Topics | coding, skills | coding, memory |
| Curated connections | 3 | 4 |
ECC — the curator's take
The kitchen-sink option, and the most popular one by a wide margin: one install gives Claude Code, Codex, Cursor, OpenCode and friends a full operating layer — session-memory hooks, learned instincts, quality gates, orch-* orchestrator commands, worktree lifecycle, security scanning — plus three genuinely good guides on token optimization, memory and agentic security. When NOT: it's maximalist. Hundreds of skills and global hooks add context weight, and the README's own top warning is about broken stacked installs — start with the minimal/no-hooks profile and never mix the plugin with the manual installer. If you only want one capability, take the surgical tool instead: claude-reflect for learning-from-corrections, pro-workflow for session memory, asm or skillkit for skill management. Watch the upsell surface (Pro app, sponsors) — the OSS core is MIT and complete.
pro-workflow — the curator's take
The most complete attack on Claude Code amnesia we've mapped: correct it once and the correction becomes a durable, searchable rule; research lands in wikis that persist and even grow via an auto-research loop; hooks add git/secret guards and cost tracking. After 50 sessions the compounding is real. Two cautions: NO license file at review time (all rights reserved by default — same gap as this author's other tools), and 34 skills + 37 hooks is a lot of surface — adopt the memory core first, audit the hooks before letting them gate your commits.