Tencent Cloud just open-sourced TencentDB Agent Memory v2.0, a self-hosted memory layer designed for teams running multiple AI coding agents. The pitch is not just retrieval. It’s governance: controlling which agent can see which memory, and which version of that memory is valid.
Four Memory Asset Types
The system ingests conversations, documents, and code, then organizes them into four distinct asset types:
- Chat Memory: persisted conversation context
- Skill: reusable procedural knowledge extracted from past sessions
- LLM-Wiki: structured factual knowledge your agents can query
- Code-Graph: a graph representation of your codebase for code-aware retrieval
All four are versioned and permissioned at the asset level, not just the database level.
️ The Governance Angle
The differentiator here is ACL-based visibility. Memory Hub narrows by team, user, agent, and visibility scope before it retrieves anything. That means different agents on the same team can operate with different memory views, and you can version-control which knowledge is active without blowing up shared context.
For teams running more than one coding agent in parallel, that kind of isolation matters. Without it, agents pick up each other’s stale or incorrect context and compound the errors.
Integration and Setup
The project is MIT licensed and self-hosted via Docker. It integrates with Claude Code, OpenClaw, Hermes, and CodeBuddy. No SaaS dependency, no vendor lock-in on the memory layer itself.
One caveat from the source: private-repo Code-Graph and automated memory routing are still being refined. Large regulated enterprises should pilot rather than standardize at this point.
