# TencentCloud/TencentDB-Agent-Memory

Source: [GitHub](https://github.com/TencentCloud/TencentDB-Agent-Memory)  
Feed7 permalink: https://feed7.dev/p/tencentdb-agent-memory-0gx8nnn  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

An open-source memory hub turns agent conversations, workflows, docs, and code into governed assets that can be reused across sessions and roles, reducing repeated project setup.

## Source Summary

TencentDB Agent Memory packages prior work into **four memory assets**: Chat Memory, Skills, Wiki, and CodeGraph. The hub adds ownership, versions, agent bindings, and private, team, or ACL-based access.

## Practical Implication

Use it to give coding and review agents different context loadouts instead of one global prompt. Memory is distilled through **L0–L3**, while detailed recall combines **BM25, vector retrieval, and RRF** under context-size and timeout limits.

## Agent-Ready Context

TencentDB Agent Memory packages prior work into **four memory assets**: Chat Memory, Skills, Wiki, and CodeGraph. The hub adds ownership, versions, agent bindings, and private, team, or ACL-based access.

Use it to give coding and review agents different context loadouts instead of one global prompt. Memory is distilled through **L0–L3**, while detailed recall combines **BM25, vector retrieval, and RRF** under context-size and timeout limits.

The Team Memory release is still a beta. Wiki and CodeGraph indexing is asynchronous, private-repository support and automatic routing remain incomplete, and current compatibility is limited to **OpenClaw, Hermes, and SDK integrations**.

## Connected Context

Feed7 judgment across 319 accumulated Signals:

This makes the proposed shared context layer more concrete by packaging governed, versioned assets with per-agent bindings, tiered distillation, and hybrid retrieval. It also exposes the gap between architecture and production readiness: routing, repository coverage, indexing latency, compatibility, and recipient-level access still constrain a portable team-memory layer.

- [WTF Is the Context Layer? The Missing Infrastructure for Production Agents — Prukalpa Sankar](https://feed7.dev/p/wtf-is-the-context-layer-the-missing-infrastructure-for-production-agent-0t47xqf) — TencentDB implements much of Atlan’s proposed shared, versioned context layer, including reusable facts, skills, ownership, and agent-specific access.
- [Skills are new features: Building Skill-Centric Harness — Yogendra Miraje, FactSet](https://feed7.dev/p/skills-are-new-features-building-skill-centric-harness-yogendra-miraje-f-0lp4c7o) — The hub’s ownership, versions, bindings, and ACLs reinforce the claim that growing skill libraries require product-level routing and governance.
- [Graphify-Labs/graphify](https://feed7.dev/p/graphify-1e0bs1f) — Graphify provides a focused precedent for the CodeGraph asset, while TencentDB places repository graphs beside other memory forms under one retrieval and governance system.
- [Wearing the Agent: From Group Chats to Glasses — Sai Krishna Rallabandi](https://feed7.dev/p/wearing-the-agent-from-group-chats-to-glasses-sai-krishna-rallabandi-102hk49) — Its recipient-aware privacy concerns sharpen the importance of TencentDB’s private, team, and ACL-based access when memory is shared across agents and users.

## Context Map

- Layer: agent
- Domains: coding
- Topics: agent-memory, skills, context-engineering

## Uncertainty

- The Team Memory release is still a beta. Wiki and CodeGraph indexing is asynchronous, private-repository support and automatic routing remain incomplete, and current compatibility is limited to **OpenClaw, Hermes, and SDK integrations**.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.