Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Mem0

AI overview

Sign in and the AI will write an overview from our coverage.

Headlines · 4

  1. Tencent Hunyuan releases GGUF quantizations of Hy-Memory-30B-A3B for llama.cpp

    Tencent Hunyuan published a GGUF repository for Hy-Memory-30B-A3B, a roughly 30B-parameter long-term-memory writer model with about 3B active parameters, aimed at local inference through llama.cpp. Three quantization levels are offered: Q6_K imatrix at 24.71 GB, Q8_0 at 31.99 GB and Q4_K_M imatrix at 18.24 GB, all under Apache-2.0. The model card reports LoCoMo Judge scores of 58.78% (154/262) for Q6_K, 57.63% for Q8_0 and 56.49% for Q4_K_M on a fixed 20% LoCoMo split using the Mem0 2.0.19 harness, with gpt-5.6-sol as answer and judge model; these figures are self-reported by the publisher and not independently replicated.

    腾讯混元 · Hugging Face · 🔥 0
  2. Proof Before Reuse limits agent memory poisoning in small study

    A small case study posted on r/MachineLearning proposes "Proof Before Reuse": a coding agent writes a skill into reusable procedural memory only after two later sessions reproduce the same change and pass its test, and the agent is shown only the lines those sessions also wrote. The study compares no memory, replay of recorded edits, naive memory (every passing session kept, with the skill chosen by Mem0's search) and the proof-before-reuse arm, running five scored sessions per arm with Claude Haiku 5.5 and Sonnet 5.5 plus a hidden verifier with 187 behavioural checks. The author reports that replay put the poison back in 30/30 repos with every test passing, naive memory exposed the poison in 3/30 sessions, and proof before reuse exposed it in 0/30, while noting the work covers one task, uses n=5 per cell, is not significant at p≈0.24 and measures exposure rather than harm.

    r/MachineLearning · 🔥 0
  3. Tencent Hunyuan open-sources Hy Memory 2.0, Hy-Memory-30B-A3B and MemHub

    Tencent Hunyuan announced Hy Memory 2.0 on October 16, open-sourcing three layers: the dedicated memory model Hy-Memory-30B-A3B, the memory framework SDK and the local MemHub app. Tencent says the framework handles chat, work and code memory and ranks first against open frameworks including Mem0, MemOS, EverOS and OpenViking on four benchmarks; it reports that Hy-Memory-30B-A3B, with about 3B active parameters, scored a 55.49 macro average across four memory harnesses versus 54.62 for Claude Opus 5. MemHub ships as a CLI and Mac app that can connect to roughly 10 tools such as WorkBuddy, Cursor, Codex and Qwen Code, while the model weights are published on Hugging Face under Apache 2.0, followed on October 18 by an FP8 version optimized for vLLM deployment. All performance figures are Tencent's own claims and have not been independently verified.

    腾讯混元 · Hugging Face · 🔥 0
  4. Cognee ships v1.6.1 with Google Drive, Gmail connectors and graph visualization

    Cognee is an open-source AI memory platform that gives agents persistent long-term memory across sessions, turning documents, code and conversations into a self-hosted, searchable knowledge graph that can run locally with small models and no cloud LLM key. Per its release notes, v1.6.1 (September 24) bundles Google Drive and Gmail OAuth connectors into the SDK, streams visualization of large graphs in chunks, and moves the GLiNER installer off the event loop; v1.6.0 supports keyless memory building and retrieval. The project reports BEAM conversational-memory scores of 0.79 at 100K tokens and 0.67 at 10M tokens, while noting the two settings use different conversations, ingestion models and retrieval procedures.

    GitHub Trending · Python · 🔥 0

Experience and discussion from the community

Share my Mem0 experienceAsk about Mem0

Nobody has shared their experience with Mem0 yet.