TencentCloud / TencentDB-Agent-Memory

### Agents remember. Humans innovate.
Installation · Supported Agents · What is it? · Team Play · Technical Implementation · Benchmark · Roadmap
**English** · 简体中文
---
> **Latest:** Team Memory Beta is evolving quickly — install it and start exploring in minutes.
# Installation
Start all three services in one go (`memory-core` + `memory-hub` + `proxy`):
 [code] 
Open the panel: http://localhost:8125.
Complete installation documentation (standalone Memory Hub deployment, Proxy + Claude Code / CodeBuddy usage, stop and cleanup, port reference, etc.) is available in **INSTALL.md** (中文: INSTALL_CN.md).
The MongoDB storage backend is **experimental** (off by default); see
INSTALL.md · MongoDB storage backend.
### Migrating data from an older version
If you're already on an older release (v1.x / v0.x) and want to bring your existing data over to v2.0.0+, we provide a migration tool:
See **Data Migration Tool (v2 → v3)** for full usage and flags. New installations can skip this.
## All Agents Share the Same Memory Server
One Proxy, unchanged protocol, zero-code integration — point the Agent's base URL to the Proxy and it's done. No plugin, hook, or MCP server is required.
 DeepSeek Harness 
 Claude Code 
 Codex 
 CodeBuddy 
 WorkBuddy 
 Hermes 
 OpenClaw 
 More frameworks coming soon... 
See **INSTALL.md** for the exact configuration steps of each client.
Don't see your favorite Agent? You can try adapting it yourself with the Generic integration guide — and we'd love a PR adding native support for it. See **CONTRIBUTING.md** to get started.
# What is TencentDB Agent Memory?
We started from a practical question: **How do you reduce repetitive work when using Agents?**
If project context has already been explained, it shouldn't need to be repeated in a new session. If documents have already been read, every Agent shouldn't have to start again from page one. A workflow that already works shouldn't have to be rediscovered next time.
Memory here means more than just "remembering conversations." **Any information that helps the next Agent avoid reinventing the wheel should be saved, organized, and reused.**
 [code] 
### Let experience accumulate, flow, and pass on to the next Agent
**Memory Hub** for Agent teams closes the loop across the entire experience lifecycle: work produces assets, assets circulate through the team, and new members can load the team's save file on day one.
1. **Automatic asset extraction**: Extract Chat Memory and Skills from conversations and tasks; convert documents and code into Wiki and CodeGraph; then manage, review, and route them consistently.
2. **Portable & multi-Agent compatible**: Memory assets are decoupled from Agent frameworks — they can move across frameworks and be shared and maintained by multiple Agents and team members.
3. **Cold-start friendly**: Import existing documents, codebases, and Agent conversation sessions. New Agent teams can start from existing experience instead of learning from scratch.
### 🧠 A brain t