EverOS is a clean take on portable memory: local-first, Markdown-native, user-owned, and self-evolving, meaning it merges and refines what it learned between sessions rather than just storing and retrieving. It carries that memory across Claude Code, Copilot, Gemini, and OpenCode, so your context follows you instead of being trapped in one tool. As a design it's genuinely nice, and for an individual developer who wants continuity across tools, portable local memory like this is exactly the right answer. A governed enterprise layer would be overkill.
But portability is the half of the memory problem that is commoditizing. Carrying memory between agents is becoming table stakes, and several projects now do it well. The half that stays hard, and the half that decides whether a revenue leader or a compliance team will ever trust an agent to write back to a system of record, is governance: what an agent is allowed to remember, which fields it can touch, under what conditions, and with what audit trail when it does. EverOS is honest about being user-owned and local-first; it doesn't claim to ship an access-control or governance framework, because that isn't the problem it set out to solve.
So the question I'd put to anyone betting on a memory layer: portability is solved-ish, but at team and enterprise scale, who governs what the memory is allowed to say?