OKF: Google's open format for agent memory
What Google's Open Knowledge Format is, how its provenance and stale_after fields handle stale and poisoned agent memory, and which OKF tool to pick.
Filtering by topic #agent-memory · clear
What Google's Open Knowledge Format is, how its provenance and stale_after fields handle stale and poisoned agent memory, and which OKF tool to pick.
Hindsight 1.0.0 against mem0 2.2.1 for agent memory on a VPS: memory model, services you run, LLM cost, MCP, licence and what self-hosting drops.
Run Hindsight 0.10.2 on your own VPS with Docker: retain, recall and reflect behind loopback, an external Postgres, and the LLM choice that sets cost.
Run the mem0 memory server on your own VPS: the real RAM floor, a Compose file that binds to localhost, TLS in front of the API, and a fully local Ollama path.
A deletion request touches more than one table. Find every copy of a user's data in a self-hosted agent memory stack, delete it, and prove it is gone.
Compartment keeps agent memory encrypted on your own machine, fully offline. What that threat model really covers, and what happens if you lose the key.
Agent memories go wrong quietly. Put an expiry on time bound facts, cascade the deletes, review the rest, and read your SQLite store with sqlite3.
Prompt injection ends with the session. Memory poisoning does not. How hostile text becomes a stored fact, and how to isolate, expire and review it.
Semantic, episodic and procedural agent memory in one table, then the half nobody writes: what each type costs to store and to re-embed on a VPS.