Sign InOpen Brain
GitHubGitHub RepoNeeds Review

TencentCloud/TencentDB-Agent-Memory

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.

GitHub · Trending today
Open Source Open MarkdownOpen JSON
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

This is a concrete implementation of shared, versioned agent context with separate memory assets, scoped bindings, progressive detail, and hybrid retrieval. It supports role-specific context instead of one global prompt, but its beta status, incomplete routing and repository support, asynchronous indexing, and limited integrations keep it from establishing a broadly portable context layer.

WTF Is the Context Layer? The Missing Infrastructure for Production Agents — Prukalpa SankarTencentDB operationalizes the proposed shared, versioned context layer through owned assets, versions, bindings, and access scopes rather than isolated per-agent memory.Skills are new features: Building Skill-Centric Harness — Yogendra Miraje, FactSetIts versioned Skills and agent bindings reinforce the view of skills as governed product features, while the beta and incomplete routing show that selection and lifecycle controls remain implementation work.Graphify-Labs/graphifyGraphify provides a more specialized project-graph approach to coding context; TencentDB’s CodeGraph places that retrieval shape inside a broader memory hub alongside chat, wiki, and skills.Wearing the Agent: From Group Chats to Glasses — Sai Krishna RallabandiTencentDB’s private, team, and ACL scopes address part of shared-agent memory governance, but the candidate’s recipient- and audience-aware disclosure requirements show that storage access control alone may not govern what an agent should reveal.
Context Map
agentcoding#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**.