더 큰 모델이 아니었다—텐센트가 공개한 AI 에이전트의 ‘기억 전용 두뇌’

The next useful upgrade for an AI agent may not be a larger language model. Tencent’s Hy Memory 2.0 separates the job of remembering from the job of answering, adding an open-source framework, a shared memory hub, and a dedicated memory-writing model that decides what should survive after a conversation ends.

The promise is immediately practical. A developer may use Codex for one task, Claude Code for another, and Cursor inside the editor. Today, each tool often behaves like a colleague with partial amnesia. Hy Memory aims to preserve selected preferences, project facts, decisions, and working patterns in a common local layer that multiple agents can use.

That does not automatically make agents smarter. A bad memory system can preserve mistakes, leak secrets, and make several tools confidently repeat the same false assumption. The important question is not whether an agent can remember more. It is whether the system can remember the right evidence, show where it came from, update it, and delete it.

The three-part stack

Hy Memory 2.0 is broader than a model checkpoint. The framework ingests interactions and organizes memories; MemHub connects memory across compatible tools; and Hy-Memory-30B-A3B acts as a specialist that extracts durable information from raw conversations.

The repository separates chat, work, and coding contexts. That boundary is sensible. A meal preference should not be mixed with a repository convention, and a confidential project decision should not casually appear in a personal assistant. Distinct memory spaces can reduce accidental contamination while still allowing explicitly approved sharing.

The dedicated model uses a mixture-of-experts design with 30 billion total parameters and roughly three billion active for a given token. Its purpose is not to replace the main assistant. It is to transform a noisy transcript into structured memory: preferences, entities, decisions, constraints, and relationships that may matter later.

Why ordinary RAG is not enough

Retrieval-augmented generation usually stores documents or chunks and searches them when a query arrives. That works well for manuals and reference material. Personal and agent memory is harder because the source is a stream of changing interactions.

Suppose a user says, “Use PostgreSQL for this project,” later explains that the decision was temporary, and finally migrates to SQLite for an embedded edition. A simple vector database may retrieve all three statements. A memory system must understand time, scope, contradiction, confidence, and replacement.

Good agent memory therefore needs writing and maintenance policies, not just search. It must decide whether a statement is durable, whether it belongs to this project, when it expires, and which newer observation supersedes it. Hy Memory’s significance is that it treats those decisions as a first-class model task.

What the benchmark does and does not prove

Tencent reports an average score of 55.49% across four memory harnesses for its specialist model, compared with 54.62% for Opus 5 under the published setup. The headline sounds like a clear win, but some category differences are only one or two hundredths of a point and the evaluation uses a fixed 20% sample.

That is not enough to declare a statistically robust victory over a frontier general model. It is enough to show that a much more specialized open model can compete at memory extraction under a defined test.

Independent evaluation should examine multilingual conversations, months-long project histories, adversarial instructions, conflicting users, deletion requests, and memories that become unsafe after permissions change. The crucial metric is not how many facts are retained. It is how often the correct memory improves an answer without exposing information that should have remained isolated.

The privacy advantage—and its limit

Running the framework locally can keep transcripts and memory stores off a third-party memory service. Apache-2.0 licensing also gives teams room to inspect and modify the stack. Those are meaningful advantages for developers handling proprietary code or personal histories.

Local does not mean safe by default. The memory database may become more sensitive than any single chat because it aggregates identities, habits, credentials accidentally pasted into tools, project structure, and decisions over time. A compromised agent with broad retrieval access could reconstruct a detailed operational profile.

Memory therefore needs access control at the item and namespace level, encryption, audit logs, retention limits, deletion propagation, and protection against prompt injection. A retrieved memory should carry provenance so the user can see which interaction created it and why the system considers it current.

How teams should test it

Start with one low-risk project rather than a universal personal memory. Define a small schema: coding conventions, approved dependencies, architectural decisions, and explicit user preferences. Exclude secrets, private messages, and unreviewed model guesses.

Create tests for contradiction and deletion. Change a preference, revoke a tool’s access, remove a repository, and verify that old memories stop influencing answers. Seed a malicious document that asks the agent to save an instruction as permanent memory and confirm that the write policy rejects it.

Compare the system against a plain retrieval baseline. Measure task completion, wrong-memory rate, stale-memory rate, retrieval latency, and user correction time. If the memory layer produces fluent but untraceable assumptions, it is making the agent more dangerous rather than more useful.

Verdict

Hy Memory 2.0 points to a real shift in agent architecture. Models are becoming interchangeable for many tasks, while persistent context remains fragmented across tools. A shared memory layer can make an assistant feel continuous even when the interface or model changes.

The breakthrough is not unlimited recall. It is the attempt to build a separate, inspectable system for selecting and governing memory. If Tencent’s stack proves reliable outside its own benchmarks, the next competition may be less about who has the biggest model and more about whose agent knows what to keep, what to forget, and when not to remember at all.