claude-reflect vs opencode-mem
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 — OpenCode 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.
Both 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.
| claude-reflect | opencode-mem | |
|---|---|---|
| Stars | 1.3k | 1.1k |
| Forks | 109 | 113 |
| Language | Python | TypeScript |
| License | MIT | — |
| Last activity | 4 months ago | 5 days ago |
| Topics | coding, memory | memory, coding |
| Curated connections | 9 | 2 |
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.
opencode-mem — the curator's take
For OpenCode users tired of re-explaining their architecture every session: auto-capture summarizes each prompt's work via a background structured-output call that reuses your existing opencode provider auth, memories inject into the first chat message, and the `.opencode-mem-project` marker file solves multi-repo workspaces properly (directory-driven identity, not env vars). A real web UI at :4747 for browsing what it learned. NOT for Claude Code — this is OpenCode-specific; pro-workflow and claude-reflect are the equivalents on that side. Auto-capture needs a provider that speaks structured output, and the default local embedding model downloads on first use. Inspired by opencode-supermemory, but local-first.