thedotmack/claude-mem

Choose this fork if you want more control and custom workflows around memory capture and worker operations, and you are comfortable giving up some upstream compatibility and provider breadth. Choose upstream if you want the newest fixes and the broadest, least-surprising feature set.

Prefer upstream unless you specifically want this repository as a private base. For adopters, the fork offers no visible advantages and is meaningfully behind current upstream fixes.

Prefer upstream unless you specifically need this exact snapshot. The fork adds no visible capabilities and is already behind on recent fixes, so it is mostly useful as a thin base for experimentation rather than as a better end-user build.

Choose this fork if you want a customized, ops-heavy variant of claude-mem with Bun migration and install/runtime changes. Choose upstream if you want the latest fixes, lower maintenance risk, and broader current compatibility.

Prefer upstream unless you specifically need this fork’s ownership model or private edits. The fork shows no clear added capability, while it lags upstream by enough commits to make missing fixes the main concern.

Choose this fork if you want the added OpenCode/worker automation features and can tolerate heavy divergence. Choose upstream if you want the most current Claude-Mem fixes, lower maintenance risk, and easier upgrades.

Choose the upstream project unless you specifically need this snapshot. This fork adds no visible capabilities and is far behind upstream, so its main value is as a frozen copy rather than a differentiated release.

This fork is effectively an upstream snapshot with no added functionality. Prefer it only if you want a personal starting point; otherwise upstream is the better choice because it is much newer and actively maintained.

Choose this fork if localization and Zhipu/GLM support matter more than staying fully current with upstream. Choose upstream if you want the broadest maintenance coverage and the newest fixes.