three different bets on memory across open source AI assistants

Three fundamentally different approaches to how knowledge should accumulate over time, each revealing something about the design philosophy of the underlying tool. Hermes Generates skills automatically after each task based on the system's own evaluation of the output. Loop closes fast, which is the appeal. Fatal flaw is that the grader and the graded are the same system, which means bad skills stay saved and reinforce across cycles. OpenClaw Memory lives in hand-written markdown skill files that define behavioral patterns and edge-case handling. Works well once heavily tuned. Most of the long-term success depends on continued skill curation, which is a real maintenance cost most people underestimate. Vellum accumulates memory through explicit user approval at each write, which prevents both the self-reinforcement trap and the manual skill tuning tax. The consensus from month-long use is that knowledge state stays intentional rather than emergent, which is what makes the system debuggable when something breaks. Imo this is the most underrated memory approach in the space because it trades ambition for reliability and wins on total time saved. Automated learning loops fail silently, manual skill systems require sustained investment, and the middle path of confirmed updates produces the fewest surprises over a month of daily use.