TencentCloud/TencentDB-Agent-MemoryPublic

TencentDB Agent Memory is a team-level memory hub for AI Agents — turning conversations, docs, and code into four reusable memory assets (Chat Memory, Skill, LLM-Wiki, Code-Graph) that are governed, shared, and equipped across agents and frameworks.

AI summary: A team-level memory hub governing chat, skills, wikis, and code graphs for AI agents.

Stars
31K
+77 today
Forks
3K
Watchers
89
Open issues
310
Open PRs
545
Contributors
~38
Commits
80
Branches
4

TypeScriptOtherCreated Apr 7, 2026Last push 10d agoLatest release v2.0.3+227 stars this week+1.4K this month

Quick answers

What is TencentDB-Agent-Memory?
A team-level memory hub governing chat, skills, wikis, and code graphs for AI agents.
What does TencentDB-Agent-Memory do?
TencentDB Agent Memory acts as a centralized, team-level memory hub that persistent context for AI agents across different frameworks. It transforms raw conversations, documentation, and source code into four distinct, reusable memory assets: Chat Memory, Skills, LLM-Wikis, and Code-Graphs. This structured approach allows teams to govern, share, and equip their agents with a standardized, long-term understanding of the project. By decoupling memory from specific agent implementations, it enables true cross-agent collaboration and institutional knowledge retention. This structured approach ensures memory is governed, shared securely, and equipped efficiently across varying organizational agent frameworks.
Who is TencentDB-Agent-Memory for?
Enterprise AI teams and developers building complex, multi-agent systems who need a robust, shared memory infrastructure. It is designed for scenarios where isolated agent memory is insufficient for team-wide productivity.
How do I get started with TencentDB-Agent-Memory?
docker-compose up -d
How popular is TencentDB-Agent-Memory on GitHub?
TencentCloud/TencentDB-Agent-Memory has 30,974 stars and 3,030 forks on GitHub, and gained 227 stars in the last 7 days.
What license does TencentDB-Agent-Memory use?
TencentCloud/TencentDB-Agent-Memory is released under the Other license.

Star history

since Jul 28, 2026
010K20K30KJul 2026Sep 2026Oct 2026Nov 2026
31K stars as of Nov 18, 2026. Measured daily since Jul 28, 2026; GitHub no longer exposes earlier star timestamps.

Update history

3 recorded
  • Nov 3, 2026New release v2.0.3 (previously v2.0.3-beta.1).
  • Oct 14, 2026New release v2.0.3-beta.1 (previously v2.0.1).
  • Oct 4, 2026Previously tracked as Tencent/TencentDB-Agent-Memory; its 1 daily snapshot and 2 trending appearances were merged into this profile. Stars: 9,340 on 2026-07-28 under the old name, 27,682 on 2026-10-04 (+18,342).

Contribution activity

commits per day, last 52 weeks
NovDecJanFebMarAprMayJunJulAugSepOctNovMonWedFri2025-11-16: 0 commits2025-11-17: 0 commits2025-11-18: 0 commits2025-11-19: 0 commits2025-11-20: 0 commits2025-11-21: 0 commits2025-11-22: 0 commits2025-11-23: 0 commits2025-11-24: 0 commits2025-11-25: 0 commits2025-11-26: 0 commits2025-11-27: 0 commits2025-11-28: 0 commits2025-11-29: 0 commits2025-11-30: 0 commits2025-12-01: 0 commits2025-12-02: 0 commits2025-12-03: 0 commits2025-12-04: 0 commits2025-12-05: 0 commits2025-12-06: 0 commits2025-12-07: 0 commits2025-12-08: 0 commits2025-12-09: 0 commits2025-12-10: 0 commits2025-12-11: 0 commits2025-12-12: 0 commits2025-12-13: 0 commits2025-12-14: 0 commits2025-12-15: 0 commits2025-12-16: 0 commits2025-12-17: 0 commits2025-12-18: 0 commits2025-12-19: 0 commits2025-12-20: 0 commits2025-12-21: 0 commits2025-12-22: 0 commits2025-12-23: 0 commits2025-12-24: 0 commits2025-12-25: 0 commits2025-12-26: 0 commits2025-12-27: 0 commits2025-12-28: 0 commits2025-12-29: 0 commits2025-12-30: 0 commits2025-12-31: 0 commits2026-01-01: 0 commits2026-01-02: 0 commits2026-01-03: 0 commits2026-01-04: 0 commits2026-01-05: 0 commits2026-01-06: 0 commits2026-01-07: 0 commits2026-01-08: 0 commits2026-01-09: 0 commits2026-01-10: 0 commits2026-01-11: 0 commits2026-01-12: 0 commits2026-01-13: 0 commits2026-01-14: 0 commits2026-01-15: 0 commits2026-01-16: 0 commits2026-01-17: 0 commits2026-01-18: 0 commits2026-01-19: 0 commits2026-01-20: 0 commits2026-01-21: 0 commits2026-01-22: 0 commits2026-01-23: 0 commits2026-01-24: 0 commits2026-01-25: 0 commits2026-01-26: 0 commits2026-01-27: 0 commits2026-01-28: 0 commits2026-01-29: 0 commits2026-01-30: 0 commits2026-01-31: 0 commits2026-02-01: 0 commits2026-02-02: 0 commits2026-02-03: 0 commits2026-02-04: 0 commits2026-02-05: 0 commits2026-02-06: 0 commits2026-02-07: 0 commits2026-02-08: 0 commits2026-02-09: 0 commits2026-02-10: 0 commits2026-02-11: 0 commits2026-02-12: 0 commits2026-02-13: 0 commits2026-02-14: 0 commits2026-02-15: 0 commits2026-02-16: 0 commits2026-02-17: 0 commits2026-02-18: 0 commits2026-02-19: 0 commits2026-02-20: 0 commits2026-02-21: 0 commits2026-02-22: 0 commits2026-02-23: 0 commits2026-02-24: 0 commits2026-02-25: 0 commits2026-02-26: 0 commits2026-02-27: 0 commits2026-02-28: 0 commits2026-03-01: 0 commits2026-03-02: 0 commits2026-03-03: 0 commits2026-03-04: 0 commits2026-03-05: 0 commits2026-03-06: 0 commits2026-03-07: 0 commits2026-03-08: 0 commits2026-03-09: 0 commits2026-03-10: 0 commits2026-03-11: 0 commits2026-03-12: 0 commits2026-03-13: 0 commits2026-03-14: 0 commits2026-03-15: 0 commits2026-03-16: 0 commits2026-03-17: 0 commits2026-03-18: 0 commits2026-03-19: 0 commits2026-03-20: 0 commits2026-03-21: 0 commits2026-03-22: 0 commits2026-03-23: 0 commits2026-03-24: 0 commits2026-03-25: 0 commits2026-03-26: 0 commits2026-03-27: 0 commits2026-03-28: 0 commits2026-03-29: 0 commits2026-03-30: 0 commits2026-03-31: 0 commits2026-04-01: 0 commits2026-04-02: 0 commits2026-04-03: 0 commits2026-04-04: 0 commits2026-04-05: 0 commits2026-04-06: 0 commits2026-04-07: 0 commits2026-04-08: 0 commits2026-04-09: 0 commits2026-04-10: 0 commits2026-04-11: 0 commits2026-04-12: 0 commits2026-04-13: 0 commits2026-04-14: 0 commits2026-04-15: 0 commits2026-04-16: 0 commits2026-04-17: 0 commits2026-04-18: 0 commits2026-04-19: 0 commits2026-04-20: 0 commits2026-04-21: 0 commits2026-04-22: 0 commits2026-04-23: 0 commits2026-04-24: 0 commits2026-04-25: 0 commits2026-04-26: 0 commits2026-04-27: 0 commits2026-04-28: 0 commits2026-04-29: 0 commits2026-04-30: 0 commits2026-05-01: 0 commits2026-05-02: 0 commits2026-05-03: 0 commits2026-05-04: 0 commits2026-05-05: 0 commits2026-05-06: 0 commits2026-05-07: 0 commits2026-05-08: 0 commits2026-05-09: 0 commits2026-05-10: 0 commits2026-05-11: 0 commits2026-05-12: 0 commits2026-05-13: 0 commits2026-05-14: 0 commits2026-05-15: 0 commits2026-05-16: 0 commits2026-05-17: 0 commits2026-05-18: 0 commits2026-05-19: 0 commits2026-05-20: 0 commits2026-05-21: 0 commits2026-05-22: 0 commits2026-05-23: 0 commits2026-05-24: 0 commits2026-05-25: 0 commits2026-05-26: 0 commits2026-05-27: 0 commits2026-05-28: 0 commits2026-05-29: 0 commits2026-05-30: 0 commits2026-05-31: 0 commits2026-06-01: 0 commits2026-06-02: 0 commits2026-06-03: 0 commits2026-06-04: 0 commits2026-06-05: 0 commits2026-06-06: 0 commits2026-06-07: 0 commits2026-06-08: 0 commits2026-06-09: 0 commits2026-06-10: 0 commits2026-06-11: 0 commits2026-06-12: 0 commits2026-06-13: 0 commits2026-06-14: 0 commits2026-06-15: 0 commits2026-06-16: 0 commits2026-06-17: 0 commits2026-06-18: 0 commits2026-06-19: 0 commits2026-06-20: 0 commits2026-06-21: 0 commits2026-06-22: 0 commits2026-06-23: 0 commits2026-06-24: 0 commits2026-06-25: 0 commits2026-06-26: 0 commits2026-06-27: 0 commits2026-06-28: 0 commits2026-06-29: 0 commits2026-06-30: 0 commits2026-07-01: 0 commits2026-07-02: 0 commits2026-07-03: 0 commits2026-07-04: 0 commits2026-07-05: 0 commits2026-07-06: 0 commits2026-07-07: 0 commits2026-07-08: 0 commits2026-07-09: 0 commits2026-07-10: 0 commits2026-07-11: 0 commits2026-07-12: 0 commits2026-07-13: 0 commits2026-07-14: 0 commits2026-07-15: 0 commits2026-07-16: 0 commits2026-07-17: 0 commits2026-07-18: 0 commits2026-07-19: 0 commits2026-07-20: 0 commits2026-07-21: 0 commits2026-07-22: 3 commits2026-07-23: 0 commits2026-07-24: 1 commit2026-07-25: 0 commits2026-07-26: 0 commits2026-07-27: 0 commits2026-07-28: 0 commits2026-07-29: 1 commit2026-07-30: 0 commits2026-07-31: 0 commits2026-08-01: 0 commits2026-08-02: 0 commits2026-08-03: 1 commit2026-08-04: 0 commits2026-08-05: 1 commit2026-08-06: 2 commits2026-08-07: 0 commits2026-08-08: 0 commits2026-08-09: 0 commits2026-08-10: 1 commit2026-08-11: 1 commit2026-08-12: 0 commits2026-08-13: 0 commits2026-08-14: 2 commits2026-08-15: 2 commits2026-08-16: 0 commits2026-08-17: 0 commits2026-08-18: 0 commits2026-08-19: 0 commits2026-08-20: 0 commits2026-08-21: 0 commits2026-08-22: 0 commits2026-08-23: 0 commits2026-08-24: 0 commits2026-08-25: 3 commits2026-08-26: 1 commit2026-08-27: 3 commits2026-08-28: 0 commits2026-08-29: 0 commits2026-08-30: 0 commits2026-08-31: 1 commit2026-09-01: 0 commits2026-09-02: 0 commits2026-09-03: 2 commits2026-09-04: 0 commits2026-09-05: 0 commits2026-09-06: 0 commits2026-09-07: 1 commit2026-09-08: 3 commits2026-09-09: 0 commits2026-09-10: 2 commits2026-09-11: 1 commit2026-09-12: 0 commits2026-09-13: 0 commits2026-09-14: 0 commits2026-09-15: 1 commit2026-09-16: 0 commits2026-09-17: 5 commits2026-09-18: 1 commit2026-09-19: 0 commits2026-09-20: 3 commits2026-09-21: 1 commit2026-09-22: 0 commits2026-09-23: 1 commit2026-09-24: 1 commit2026-09-25: 0 commits2026-09-26: 1 commit2026-09-27: 0 commits2026-09-28: 2 commits2026-09-29: 0 commits2026-09-30: 0 commits2026-10-01: 0 commits2026-10-02: 0 commits2026-10-03: 0 commits2026-10-04: 0 commits2026-10-05: 0 commits2026-10-06: 0 commits2026-10-07: 0 commits2026-10-08: 0 commits2026-10-09: 2 commits2026-10-10: 1 commit2026-10-11: 0 commits2026-10-12: 3 commits2026-10-13: 1 commit2026-10-14: 2 commits2026-10-15: 3 commits2026-10-16: 0 commits2026-10-17: 0 commits2026-10-18: 0 commits2026-10-19: 1 commit2026-10-20: 1 commit2026-10-21: 2 commits2026-10-22: 0 commits2026-10-23: 0 commits2026-10-24: 0 commits2026-10-25: 0 commits2026-10-26: 2 commits2026-10-27: 0 commits2026-10-28: 4 commits2026-10-29: 0 commits2026-10-30: 0 commits2026-10-31: 0 commits2026-11-01: 0 commits2026-11-02: 0 commits2026-11-03: 0 commits2026-11-04: 1 commit2026-11-05: 0 commits2026-11-06: 0 commits2026-11-07: 0 commits2026-11-08: 0 commits2026-11-09: 1 commit2026-11-10: 2 commits2026-11-11: 0 commits2026-11-12: 0 commits2026-11-13: 0 commits2026-11-14: 0 commits
74 commits in the last yearLessMore

Signals and awards

derived from tracked data
  • Widely adopted

    30,974 stars

  • Continuous integration

    Automated checks passing

  • Repeat trending

    38 trending appearances

What TencentDB-Agent-Memory does

TencentDB Agent Memory acts as a centralized, team-level memory hub that persistent context for AI agents across different frameworks. It transforms raw conversations, documentation, and source code into four distinct, reusable memory assets: Chat Memory, Skills, LLM-Wikis, and Code-Graphs. This structured approach allows teams to govern, share, and equip their agents with a standardized, long-term understanding of the project. By decoupling memory from specific agent implementations, it enables true cross-agent collaboration and institutional knowledge retention. This structured approach ensures memory is governed, shared securely, and equipped efficiently across varying organizational agent frameworks.

Enterprise AI teams and developers building complex, multi-agent systems who need a robust, shared memory infrastructure. It is designed for scenarios where isolated agent memory is insufficient for team-wide productivity.

  • Four-asset taxonomy: Categorizes knowledge into Chat Memory, Skills, LLM-Wikis, and Code-Graphs for optimized retrieval.
  • Team-level governance: Allows teams to manage, audit, and share memory assets centrally rather than in isolated silos.
  • Cross-framework compatibility: Equips agents built on different platforms with a unified memory source.
  • Long-term persistence: Ensures context is retained indefinitely, enabling agents to learn and adapt over time.
  • Vector search integration: Employs embedding-based retrieval to surface relevant context quickly during agent operations.
  • Memory Governance: Enforces strict data access and sharing protocols across different team agents.

Where teams use it

Institutional knowledge sharing

Allow a newly deployed agent to instantly access the established Code-Graph and LLM-Wiki built by previous agents.

Cross-agent collaboration

Enable a debugging agent to read the Chat Memory and Skills learned by a distinct code-generation agent.

Centralized context governance

Audit and refine the knowledge base your agents use, ensuring they operate on accurate, team-approved information.

Long-running autonomous tasks

Provide agents with the persistent memory required to execute complex, multi-day workflows without losing context.

Knowledge Continuity

Enterprise teams ensure conversational context and code snippets are preserved seamlessly between shift handoffs.

Getting started: docker-compose up -d

README

feat/server_team branch

memoryhub_demo.mov

Installation

Start all three services in one go (memory-core + memory-hub + proxy):

git clone https://github.com/TencentCloud/TencentDB-Agent-Memory.git
cd TencentDB-Agent-Memory/deploy/global-images
cp .env.example .env
$EDITOR .env       # Fill in two sets of LLM parameters (memory group + proxy group)
./start-all.sh     # Launch everything with one command; when finished, it prints a one-liner you can paste directly into Claude

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 configure its User Key. Most clients don't require a plugin, hook, or MCP server.


DeepSeek Harness

Claude Code

Codex

CodeBuddy

WorkBuddy

Hermes

OpenClaw
More frameworks coming soon...

OpenCode

Pi

See INSTALL.md for links to the exact configuration steps of each client.

OpenCode has a ready-to-use adapter configuration, and Pi uses the pi-plugin extension to connect through OpenAI Chat Completions. After binding a session, you can save a Team, Agent, and Task combination as the default for new sessions.

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.

Best Practices

Once you've deployed the stack and connected your Agents, use the guide to set up a team, import and assign memory assets, and see how well they work on a real task.

See the Best Practices guide.

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.

Existing information → Reusable memory assets → Fewer turns → Less rework → More stable results and higher efficiency

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 that remembers people and context

  • Chat Memory retains preferences, facts, decisions, and interaction history.
  • Session bindings and permissions determine which memories an Agent can access. When an Agent returns to the same work, it can reuse the context.
  • L0 Conversation → L1 Atom → L2 Scenario → L3 Persona — raw conversations are distilled layer by layer.

image.png

"Don't refactor the old auth module — mobile is still using it." — Context this costly shouldn't depend on humans repeating it every time.

⚡ A Skill library that accumulates expertise

  • After completing complex work, Agents can extract and manage reusable Skills from conversations and tool calls, and import them into the context of a designated Agent when needed. Skills can be edited and exported from the panel.
  • A Skill isn't just a prompt snippet; it has versions, resource files, trigger boundaries, execution steps, and validation rules.
  • Personal Skills are private by default; they can be shared with the team and assigned to other Agents.

image.png

Troubleshooting, code review, release checklists — learn it once, and the whole team can use it.

📖 A knowledge map that reads both docs and code

  • Wiki turns product docs, design specs, and ops runbooks into structured pages with a link graph. It supports Markdown, plain text, HTML, Word, Excel, PowerPoint, and PDF. (Inspired by Karpathy's LLM knowledge base.)

image.png

  • CodeGraph indexes code symbols, files, call relationships, and impact paths.

image.png

  • Agents can search, read, inspect callers/callees, and perform impact analysis before modifying code.

Wiki keeps Agents from reading every file list before getting to work. CodeGraph doesn't just tell them "the code is here" — it tells them "changing this might affect those."

🛡️ A team memory panel controlled by humans

  • Create teams and Agents in Memory Hub; review, share, and equip memory assets.
  • Manage ownership, versions, status, visibility, usage counts, and Agent bindings in one place.
  • private belongs strictly to the Owner; team is visible to all team members; restricted grants precise access via User / Role / Agent ACLs.
  • Two role layers: global System Admin manages users and teams (creating teams, adding members) and can also use Wiki, CodeGraph, Skill, and other asset management features; Team-level roles include Admin (team manager) and Member (regular member), responsible for asset collaboration and access control within a team. Asset ownership is tracked via Owner — the Owner automatically has management permissions for their assets.

image.png

Cold Start: Load the Save File, Then Get to Work

Most Agents' first task is re-learning your project. TencentDB Agent Memory turns the learning cost you've already paid into a save file:

Cold Start: import codebase, docs, and history into Memory Hub

Admins can configure a default Agent template for the team so new members can pick up the team's way of working.

Specifically, you can import codebases and documents in the panel and use the client import script for past conversation sessions:

  • Codebases: Import public repositories or private repositories with configured credentials — CodeGraph automatically indexes symbols, files, call relationships, and impact paths.
  • Documents & files: Import relevant docs and files, including from configured external sources — Wiki automatically generates structured pages with a link graph.
  • Conversation sessions: Use the local asset import script to import past sessions from supported clients. By default, the script triggers both Skill and Chat Memory extraction; you can also choose to trigger just one.

Stop retraining every Agent. Give it the save file.

One Play Style: Build a Growing Agent Team for a One-Person Company

Open Memory Hub and create a team:

Tiny but Serious Inc.
├── 👤 You · Set goals / Make decisions
├── 🔭 Scout · Research / Find opportunities
├── 🛠 Builder · Write code / Build products
├── 🧪 Reviewer · Test / Find issues
└── 🧠 Agent Memory · Preserve the team's experience

You're not opening four disconnected chat windows — you're assembling a squad with different roles that can inherit the team's accumulated experience.

Recruit first, then equip

🔭 Scout
   ├── User interview Chat Memory
   ├── Market research Wiki
   └── Competitive analysis Skill

🛠 Builder
   ├── Product Wiki
   ├── Project CodeGraph
   └── Feature Delivery Skill

🧪 Reviewer
   ├── Historical incident Chat Memory
   ├── Project CodeGraph
   └── Release Checklist Skill

Different roles, different loadouts. Less noise — give each Agent the memory assets it actually needs to get work done.

The company can be tiny. Experience can compound forever.

Memory Assets, Not a Chat Log Warehouse

RAG answers "what can be found?" Team Memory also answers "who can use it, which version is valid, and which Agent should receive it."

Chat History Standard RAG TencentDB Agent Memory
Cross-session user understanding △ △ ✅ Chat Memory
Distilled executable experience — — ✅ Skill
Document structure & relationships — △ Chunk retrieval ✅ Wiki + Link Graph
Code call graphs & impact scope — △ Text match ✅ CodeGraph
Ownership / Version / Status — — ✅
Team sharing & Agent loadout — — ✅
Private / Team / ACL — △ ✅

Memory Hub Is Not a Display Board — It's a Control Panel

Play Style What you do in the Hub
Team Up Create teams, add people and Agents, define sharing boundaries
Asset Library Browse, search, review, and manage Chat Memory, Skills, Wiki, and CodeGraph
Agent Loadout Bind different memory assets to different Agents; adjust priority and usage mode; configure the team's default Agent template
Knowledge Workshop Build Wiki and CodeGraph; monitor processing status and asset metadata
Access Control Switch between private, team, and ACL-based access; revoke sharing when needed
Asset Usage Analytics Enable optional analytics to see how often memory, skill, and knowledge tools are called

When you open an asset, what matters is not just "what it says," but also "where it came from, which version it is, who it's assigned to, and whether it's been used recently."

Every Loop Gains Experience

Every Loop Gains Experience: continuous accumulation, making every use smarter

Memory doesn't run the Agent loop; it ensures the next iteration inherits the previous one's results: valuable interactions stay in Chat Memory, proven workflows are distilled into Skills, and document/code changes are updated through Wiki ingest and CodeGraph sync.

Without Memory, loops may just repeat faster. With inherited memory, each iteration has the chance to be better than the last.

One Agent Team: Shared Experience, Not Shared Privacy

New Chat Memory and Skills are private by default. Sharing is an explicit action, not a default leak.

Visibility Semantics
private Only the Owner can read — not even team admins
team Team members can read; the Owner / Admin can manage
restricted Precise access via User / Role / Agent ACL
agent For targeted equipping of Agents within the same team

You can assign the "Release Skill" to the Release Agent, the "Architecture Wiki" to all development Agents, and CodeGraph to Coder and Reviewer.

Technical Implementation

TencentDB Agent Memory doesn't aim to "store everything." It solves three problems: what's worth keeping, who can use it, and how to retrieve less while retrieving the right things next time.

Technical overview: layering (L0–L3), Memory Assets, Memory Hub, identity-based assembly for Agents

1. Memory isn't flat records — it grows in layers

Conversations are first saved as L0, then refined by an async pipeline into multiple levels of granularity:

Layer What it stores Primary use
L0 Conversation Raw conversations with full context Verify exact wording, timestamps, and sources
L1 Atom Facts, preferences, constraints, and events extracted from conversations Precise recall of actionable information
L2 Scenario Knowledge blocks organized around projects or scenarios Quickly restore a working context
L3 Core / Persona Long-term profiles, stable patterns, and high-level cognition Let Agents rapidly enter a user's and team's context

Both generation and retrieval are layered: normally, L2/L3 provide a quick context bootstrap; when specific facts are needed, BM25 + vector retrieval + RRF fall back to L1/L0. Results are further capped by item count, character budget, and timeout limits to prevent memory from overwhelming the context window.

2. Memory isn't a global prompt — it's the Agent's loadout

Chat Memory, Skills, Wiki, and CodeGraph are all registered uniformly as Memory Assets. Memory Hub uses Fixed Binding + ACL to determine which assets a given Agent can use: first narrow the permission scope by Team, User, Agent, and visibility, then retrieve based on the current query.

This lets teams share experience without exposing all their private information; switching Agents or frameworks only requires re-equipping, not retraining.

3. Knowledge isn't injected wholesale — it's called on demand

Documents are organized into searchable Wiki pages that support link-graph drill-down; codebases are indexed into CodeGraph assets containing files, symbols, and call relationships. Agents call authorized knowledge tools on demand to read relevant pages, source code, or impact paths. The Knowledge service exposes /v3/tools/list and /v3/tools/call for integrations.

This makes documents and code part of memory as well — but they remain available tools that only enter context when truly needed.

Benchmark

Benchmark Without TencentDB Agent Memory With it enabled Relative improvement
PersonaMem 48% 76% +59%

PersonaMem tests whether an Agent can correctly understand and apply user information after extended interactions.

Notes

  • Wiki and CodeGraph are built asynchronously; allow some processing time before they reach ready status.
  • CodeGraph supports public HTTPS repositories and private repositories with configured credentials. To clone a private repository over SSH, get the public key from the panel and grant it access on your code hosting platform.
  • The Hub supports manual asset binding. On-demand Skill selection in the Proxy is off by default. Once you enable it and configure a selection strategy, the Proxy can select up to one relevant Skill to load per turn.

Related Documentation

Agent Memory doesn't have a settled standard yet. Bug reports, documentation, benchmarks, new framework adapters, and more creative Memory Hub use cases are all welcome.


Roadmap

v2.0.3 adds default session bindings and support for rich document formats in Wiki. See GitHub Releases for the latest stable release and CHANGELOG.md for the release history.

👉 See earlier plans in ROADMAP.md (中文: ROADMAP_CN.md).


Acknowledgements

TencentDB Agent Memory stands on the shoulders of the open-source community:

  • CodeGraph — our CodeGraph asset module uses code from this project. Its design of a pre-indexed code graph is the foundation of our implementation.
  • Hermes Agent (Nous Research) — our Skill asset management uses part of the Skill-related code from Hermes Agent and builds further optimizations base on it.
  • "LLM Wiki" by Andrej Karpathy — the idea of treating documentation as an LLM-maintained, incrementally growing knowledge artifact directly informed how our Wiki layer is built and kept up to date.

We are grateful to the authors and contributors of these projects.


Community & Contributing

We welcome contributions of all kinds — bug reports, feature suggestions, documentation fixes, benchmark reproductions, ecosystem integrations, or pull requests. Agent memory is far from settled, and we hope to build it together with the community.

  • 🐞 Found a bug or have a question? Open an issue in GitHub Issues — we respond within 24 hours.
  • 💡 Have an idea to share? Start a thread in GitHub Discussions.
  • 🛠️ Want to contribute code? Please read CONTRIBUTING.md first.
  • 💬 Want to chat with us? Join our Discord community and talk to the core developers directly.
  • ☁️ Try the hosted version: Tencent Cloud Agent Memory is now available.
  • 💬 Want to join the community? Scan the QR code to join the Agent Memory WeChat group and talk directly with the early developers.

Agent Memory WeChat community QR code


Let the path the team has walked become the next Agent's starting line.


✨ Contributors

💡 Thanks to the following contributors building with us — you make TencentDB Agent Memory better.

If TencentDB Agent Memory has been helpful to you, please consider starring the project.
If you have any suggestions, feel free to open an issue for discussion.
Star TencentDB Agent Memory

Star History

Star History Chart


MIT © TencentDB Agent Memory Team

View on GitHub

Recent activity

commits and pull requests

Releases and announcements

22 total
  1. v2.0.3v2.0.3Oct 26, 2026

    ## [2.0.3] - 2026-10-26 v2.0.3 发布,相比 v2.0.3-beta.1 新增会话默认绑定与 Wiki 富文档,并把未单独配置超时的上游等待时间从 10 分钟改为 1 小时。同时修复 DeepSeek Harness 辅助接口、历史记忆时间格式、安装脚本、面板交互、Knowledge 启动,以及代理在 Redis 中断后不能自行恢复的问题。 > **产品定位**:让 Agent 的经验、文档、代码沉淀成可复用资产,让下一位 Agent > 直接读档。详见 [README_CN.md](./README_CN.md)。 ### 🔁 会话默认绑定 - 用户可为自己保存 Team、Agent、Task 的默认组合。新会话会直接使用该组合,不再每次弹出选择 - 未设置时仍走原来的选择流程;默认组合失效时自动回到原流程,并说明原因 - 可在会话中锁定或解锁该默认组合,避免后续会话被意外改掉 ### 📄 Wiki 富文档 - Wiki 新增 Word、Excel、PowerPoint、PDF 等富文档的导入、预览和内容抽取 - 原有 Markdown、文本和 HTML 导入保持可用;修复 Markdown 粘贴在部分情况下导入失败的问题 ### ⏱️ 长回复不再被提前截断 - 未单独配置超时时,上游等待时间由 10 分钟改为 1 小时;已填写 `forwardTimeoutMs` 的配置保持不变 - 流式回复连续 60 秒没有新内容时只记录告警,不再因此中断 ### 🐛 修复 - 修复 DeepSeek Harness 的 token 计数、embeddings 等辅助接口返回 404 的问题 - 修复部分历史记忆因时间格式异常而无法生成 L1 记忆的问题 - 修复 macOS 上一键安装脚本遇到中文标点时退出的问题 - 修复面板拖拽结束后鼠标样式和文本选择未恢复的问题 - 修复面板标签页关闭键无法用键盘激活的问题 - 修复生成的 User Key 复制失败时没有提示的问题 - 修复 Knowledge 服务因 OpenTelemetry 依赖版本漂移而无法启动的问题 - 修复代理在 Redis 中断后不能自行恢复、必须重启进程的问题。短暂中断仍短暂排队;时间稍长则立即降级,不把请求拖住

  2. v2.0.3-beta.1v2.0.3-beta.1Oct 13, 2026

    ## [2.0.3-beta.1] - 2026-10-13 v2.0.3-beta.1 发布,相比 v2.0.2 新增可插拔的决策服务、技能按需选择与会话轨迹 记录能力,并补齐代码知识库的 SSH 克隆与可观测性信息。以上新能力均默认关闭, 旧配置无需修改、行为与之前保持一致。 > **产品定位**:让 Agent 的经验、文档、代码沉淀成可复用资产,让下一位 Agent > 直接读档。详见 [README_CN.md](./README_CN.md)。 ### 🧩 可插拔决策服务(默认关闭) Skill 选择与 Memory L3 更新判定统一收敛到决策服务,可灵活替换决策来源: - 通过统一的决策服务接口调用,内置 JEV,也可接入其他 decision API - 配置用 `provider` 指定(默认 `jev`),旧配置无需修改 - 默认不调用 JEV,行为与之前一致;开启后即使决策服务调用失败, 也不影响正常对话与记忆写入 ### 🧰 技能(Skill)按需选择(默认关闭) - 开启后由 Proxy 每轮自动选出合适的技能,通过一次客户端工具调用加载 - 不再向系统提示词注入完整技能目录,减少提示词开销 ### 📼 会话轨迹记录 - Proxy 在每轮对话结束后,把发往上游的消息与模型回复记录到 MemoryCore (新增 `/v3/session/add`,写入本地存储) - 随 `tdai.enabled` 开启 ### 🧠 代码知识库 - 私有代码仓支持 SSH 克隆(含非 22 端口),在面板获取 SSH 公钥后即可建图 ### 📈 可观测性 - `/health` 新增 `ftsAvailable`,便于排查 BM25 关键词召回不可用的问题 - LLM 调用失败日志补充状态码、URL 与响应内容

  3. v2.0.2v2.0.2Oct 9, 2026

    ## [2.0.2] - 2026-10-09 > **产品定位**:让 Agent 的经验、文档、代码沉淀成可复用资产,让下一位 Agent > 直接读档。详见 [README_CN.md](./README_CN.md)。 ### 🗄️ 存储后端可扩展 · 支持 MongoDB 团队记忆不再绑定单一数据底座,MongoDB 后端能力进一步补全: - 新增 memory-prompt 与 generation-ref 两类存储,覆盖更多记忆数据结构 - 一键入口 `./start-all-mongo.sh` 会把 `STORE_MODE` 持久化写入 `.env`,后续启动 保持同一后端,不再每次重复配置 - 修复索引冲突场景的自愈能力,重复的默认/抽取记录不再导致启动报错 ### 🔀 更多客户端接入 - **OpenCode** 新增官方 Memory adapter 配置包(含 `opencode.json` 与接入文档),按说明配置即可接入,无需编写插件代码 - **OpenCode** 支持 2.0 的 v2 provider 配置结构,新版客户端可直接复用官方 `opencode.v2.json` - **DeepSeek Harness** 新增 dsh 桌面端适配,配置方式可参考 `./agents/dsh/README.md` 中 1.6 的部分 - 新增 **Pi** 客户端接入(类似 Codex 的 AI Agent 客户端,走 OpenAI Chat 协议) ### 🧠 外部源导入(Wiki / 代码 / 任务) - 新增从外部任务管理系统导入 Task 的能力,任务卡片直接展示来源、支持 ID 复制与分页 - 新增外部代码源(私有仓)注册与凭据隔离,各团队持有独立凭据、互不可见 - 新增 Wiki 外部来源导入,与代码源、任务源一起补齐外部资产导入链路 ### 🧰 技能(Skill)体验优化 - 冷启动批量技能抽取新增严格模式,抽取质量更可控 - 技能抽取自动跟随用户语言,生成内容更贴合使用习惯 - 技能列表支持按使用活跃度排序,高频技能更容易被找到 ### 🎛️ Memory Hub 面板 - 任务卡片支持来源展示、ID 复制与分页优化,批量导入交互更顺畅 - 手动刷新时自动重置时间筛选,新产生的记忆能即时看到 ### 🔄 会话与接入体验 - 会话引导在更多客户端下更稳定:自动选中唯一 Agent、资产确认更精准、预设失败时 自动绕过而非卡住 - 修复 WorkBuddy 并行子代理反复弹窗的问题,会话归一更稳健 - 修复多种客户端下记忆命令、工具结果污染、历史消息重复等影响体验的问题 ###

  4. v1.0.3v1.0.3Sep 22, 2026pre-release

    ## [1.0.3] - 2026-09-22 ### 🐛 修复 #### OpenClaw 宿主兼容 - **兼容 OpenClaw 9.5**:适配新版宿主的 gateway-ized 插件安装流程与 sqlite-vec 加载方式,并前向兼容旧版本(8.2 / 9.4)。 - **修复首次 install 缺少 `enabled` 字段**:OpenClaw 9.5 在 gateway 进程内执行 `plugins install`,存在竞态导致插件首次安装缺少 `enabled` 配置。采用版本分流:`>= 9.5` 延迟 60s + `manualPatch` 直写文件,`< 9.5` 保持立即写入 + restart 原行为。 - **修复 sqlite-vec native 扩展加载失败**:OpenClaw 9.5 将插件依赖 staged 到隔离的 `package-N` 目录,原有 `sqliteVec.load` 路径失效。新增「先新后旧」回退:优先定位 `package-N` 嵌套的 `vec0.so` 直连 `loadExtension`,失败回退原 `sqliteVec.load`;无条件加载失败即降级(degraded)保持原行为。

  5. v2.0.2-beta.3v2.0.2-beta.3Sep 21, 2026pre-release

    ## [2.0.2-beta.3] - 2026-09-21 v2.0.2-beta.3 发布,相比 v2.0.1 新增可选的 MongoDB 存储后端、更丰富的面板登录方式、 全新的数据分析与可观测能力,并优化了技能展示、会话接入体验,修复了记忆召回、 多团队切换等若干问题。 > **产品定位**:让 Agent 的经验、文档、代码沉淀成可复用资产,让下一位 Agent > 直接读档。详见 [README_CN.md](./README_CN.md)。 ### 🗄️ 存储后端可扩展 · 支持 MongoDB 团队记忆不再绑定单一存储,数据底座可按需选择: - 新增 MongoDB 作为可选后端,大规模团队、高并发场景下更稳、更易横向扩展 - 本地 / 开源镜像新增一键 MongoDB 模式入口,部署时可按需切换存储方案 - 写入策略更稳健,数据一致性得到保障,减少高负载下的写入隐患 ### 🔐 登录方式更丰富 - 面板新增企业登录能力,适配内部办公账号体系,登录更省心 - 账号鉴权更稳健,身份识别更准确 ### 📊 数据分析与可观测性 - 全新数据分析页,团队使用情况一目了然,辅助你判断记忆资产的沉淀效果 - 关键环节补充埋点与可观测数据,运维排查更直观 ### 🧰 技能(Skill)体验优化 - 技能检索与展示更结构化,信息更清晰、调用更稳定 - 历史遗留的异常技能数据自动修复,旧资产无缝兼容 ### 🔄 会话与接入体验 - 更多客户端接入更顺畅,文字模式客户端也能开箱即用 - 团队 / Agent 选择列表完整展示,团队较多时不再漏选 - 会话重置完成提示更清晰 ### 🐛 修复 - 修复部分场景下记忆召回为空、检索降级不生效的问题 - 修复个别情况下记忆解析失败、历史消息重复的问题 - 修复多团队切换时列表被截断、显示不全的问题 - 修复部署脚本在部分环境下的兼容性问题

Code frequency

additions and deletions
+201.2K-201.2KWeek of 2026-07-19: +201,226 linesWeek of 2026-07-19: -13 linesWeek of 2026-07-26: +1 linesWeek of 2026-07-26: -1 linesWeek of 2026-08-02: +17,691 linesWeek of 2026-08-02: -6,668 linesWeek of 2026-08-09: +36,946 linesWeek of 2026-08-09: -8,480 linesWeek of 2026-08-16: +0 linesWeek of 2026-08-16: -0 linesWeek of 2026-08-23: +42,423 linesWeek of 2026-08-23: -23,259 linesWeek of 2026-08-30: +5 linesWeek of 2026-08-30: -4 linesWeek of 2026-09-06: +37,805 linesWeek of 2026-09-06: -10,918 linesWeek of 2026-09-13: +232 linesWeek of 2026-09-13: -24 linesWeek of 2026-09-20: +168 linesWeek of 2026-09-20: -81 linesWeek of 2026-09-27: +402 linesWeek of 2026-09-27: -97 linesWeek of 2026-10-04: +33,066 linesWeek of 2026-10-04: -11,455 linesWeek of 2026-10-11: +10,735 linesWeek of 2026-10-11: -503 linesWeek of 2026-10-18: +326 linesWeek of 2026-10-18: -15 linesWeek of 2026-10-25: +18,941 linesWeek of 2026-10-25: -2,549 linesWeek of 2026-11-01: +2 linesWeek of 2026-11-01: -2 linesWeek of 2026-11-08: +974 linesWeek of 2026-11-08: -127 linesJul 19, 2026Nov 8, 2026
+400.9K lines added, -64.2K removed over the last year.

Commits per week

last 52 weeks
90Week of 2025-11-16: 0 commitsWeek of 2025-11-23: 0 commitsWeek of 2025-11-30: 0 commitsWeek of 2025-12-07: 0 commitsWeek of 2025-12-14: 0 commitsWeek of 2025-12-21: 0 commitsWeek of 2025-12-28: 0 commitsWeek of 2026-01-04: 0 commitsWeek of 2026-01-11: 0 commitsWeek of 2026-01-18: 0 commitsWeek of 2026-01-25: 0 commitsWeek of 2026-02-01: 0 commitsWeek of 2026-02-08: 0 commitsWeek of 2026-02-15: 0 commitsWeek of 2026-02-22: 0 commitsWeek of 2026-03-01: 0 commitsWeek of 2026-03-08: 0 commitsWeek of 2026-03-15: 0 commitsWeek of 2026-03-22: 0 commitsWeek of 2026-03-29: 0 commitsWeek of 2026-04-05: 0 commitsWeek of 2026-04-12: 0 commitsWeek of 2026-04-19: 0 commitsWeek of 2026-04-26: 0 commitsWeek of 2026-05-03: 0 commitsWeek of 2026-05-10: 0 commitsWeek of 2026-05-17: 0 commitsWeek of 2026-05-24: 0 commitsWeek of 2026-05-31: 0 commitsWeek of 2026-06-07: 0 commitsWeek of 2026-06-14: 0 commitsWeek of 2026-06-21: 0 commitsWeek of 2026-06-28: 0 commitsWeek of 2026-07-05: 0 commitsWeek of 2026-07-12: 0 commitsWeek of 2026-07-19: 4 commitsWeek of 2026-07-26: 1 commitsWeek of 2026-08-02: 4 commitsWeek of 2026-08-09: 6 commitsWeek of 2026-08-16: 0 commitsWeek of 2026-08-23: 7 commitsWeek of 2026-08-30: 3 commitsWeek of 2026-09-06: 7 commitsWeek of 2026-09-13: 7 commitsWeek of 2026-09-20: 7 commitsWeek of 2026-09-27: 2 commitsWeek of 2026-10-04: 3 commitsWeek of 2026-10-11: 9 commitsWeek of 2026-10-18: 4 commitsWeek of 2026-10-25: 6 commitsWeek of 2026-11-01: 1 commitsWeek of 2026-11-08: 3 commitsNov 16, 2025Nov 8, 2026
74 commits in the last 52 weeks.

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 0 commitsSun 1:00 — 0 commitsSun 2:00 — 0 commitsSun 3:00 — 0 commitsSun 4:00 — 0 commitsSun 5:00 — 0 commitsSun 6:00 — 0 commitsSun 7:00 — 0 commitsSun 8:00 — 0 commitsSun 9:00 — 0 commitsSun 10:00 — 0 commitsSun 11:00 — 0 commitsSun 12:00 — 0 commitsSun 13:00 — 0 commitsSun 14:00 — 0 commitsSun 15:00 — 0 commitsSun 16:00 — 0 commitsSun 17:00 — 2 commitsSun 18:00 — 1 commitsSun 19:00 — 0 commitsSun 20:00 — 0 commitsSun 21:00 — 0 commitsSun 22:00 — 0 commitsSun 23:00 — 0 commitsMon 0:00 — 0 commitsMon 1:00 — 0 commitsMon 2:00 — 0 commitsMon 3:00 — 0 commitsMon 4:00 — 0 commitsMon 5:00 — 0 commitsMon 6:00 — 0 commitsMon 7:00 — 0 commitsMon 8:00 — 0 commitsMon 9:00 — 0 commitsMon 10:00 — 0 commitsMon 11:00 — 0 commitsMon 12:00 — 1 commitsMon 13:00 — 0 commitsMon 14:00 — 0 commitsMon 15:00 — 3 commitsMon 16:00 — 3 commitsMon 17:00 — 2 commitsMon 18:00 — 1 commitsMon 19:00 — 3 commitsMon 20:00 — 1 commitsMon 21:00 — 0 commitsMon 22:00 — 0 commitsMon 23:00 — 0 commitsTue 0:00 — 0 commitsTue 1:00 — 0 commitsTue 2:00 — 0 commitsTue 3:00 — 0 commitsTue 4:00 — 0 commitsTue 5:00 — 0 commitsTue 6:00 — 0 commitsTue 7:00 — 0 commitsTue 8:00 — 0 commitsTue 9:00 — 0 commitsTue 10:00 — 0 commitsTue 11:00 — 1 commitsTue 12:00 — 0 commitsTue 13:00 — 0 commitsTue 14:00 — 0 commitsTue 15:00 — 1 commitsTue 16:00 — 0 commitsTue 17:00 — 1 commitsTue 18:00 — 0 commitsTue 19:00 — 0 commitsTue 20:00 — 3 commitsTue 21:00 — 5 commitsTue 22:00 — 1 commitsTue 23:00 — 0 commitsWed 0:00 — 0 commitsWed 1:00 — 0 commitsWed 2:00 — 0 commitsWed 3:00 — 0 commitsWed 4:00 — 0 commitsWed 5:00 — 0 commitsWed 6:00 — 0 commitsWed 7:00 — 0 commitsWed 8:00 — 0 commitsWed 9:00 — 0 commitsWed 10:00 — 3 commitsWed 11:00 — 1 commitsWed 12:00 — 0 commitsWed 13:00 — 0 commitsWed 14:00 — 1 commitsWed 15:00 — 2 commitsWed 16:00 — 2 commitsWed 17:00 — 1 commitsWed 18:00 — 2 commitsWed 19:00 — 1 commitsWed 20:00 — 1 commitsWed 21:00 — 0 commitsWed 22:00 — 2 commitsWed 23:00 — 1 commitsThu 0:00 — 0 commitsThu 1:00 — 0 commitsThu 2:00 — 0 commitsThu 3:00 — 0 commitsThu 4:00 — 0 commitsThu 5:00 — 1 commitsThu 6:00 — 0 commitsThu 7:00 — 0 commitsThu 8:00 — 3 commitsThu 9:00 — 0 commitsThu 10:00 — 3 commitsThu 11:00 — 0 commitsThu 12:00 — 1 commitsThu 13:00 — 0 commitsThu 14:00 — 2 commitsThu 15:00 — 0 commitsThu 16:00 — 0 commitsThu 17:00 — 0 commitsThu 18:00 — 1 commitsThu 19:00 — 0 commitsThu 20:00 — 7 commitsThu 21:00 — 0 commitsThu 22:00 — 0 commitsThu 23:00 — 0 commitsFri 0:00 — 0 commitsFri 1:00 — 0 commitsFri 2:00 — 0 commitsFri 3:00 — 0 commitsFri 4:00 — 0 commitsFri 5:00 — 0 commitsFri 6:00 — 0 commitsFri 7:00 — 0 commitsFri 8:00 — 0 commitsFri 9:00 — 0 commitsFri 10:00 — 0 commitsFri 11:00 — 0 commitsFri 12:00 — 0 commitsFri 13:00 — 0 commitsFri 14:00 — 0 commitsFri 15:00 — 1 commitsFri 16:00 — 3 commitsFri 17:00 — 1 commitsFri 18:00 — 0 commitsFri 19:00 — 0 commitsFri 20:00 — 2 commitsFri 21:00 — 0 commitsFri 22:00 — 0 commitsFri 23:00 — 0 commitsSat 0:00 — 0 commitsSat 1:00 — 1 commitsSat 2:00 — 0 commitsSat 3:00 — 0 commitsSat 4:00 — 0 commitsSat 5:00 — 0 commitsSat 6:00 — 0 commitsSat 7:00 — 0 commitsSat 8:00 — 0 commitsSat 9:00 — 0 commitsSat 10:00 — 1 commitsSat 11:00 — 0 commitsSat 12:00 — 0 commitsSat 13:00 — 0 commitsSat 14:00 — 0 commitsSat 15:00 — 0 commitsSat 16:00 — 1 commitsSat 17:00 — 0 commitsSat 18:00 — 1 commitsSat 19:00 — 0 commitsSat 20:00 — 0 commitsSat 21:00 — 0 commitsSat 22:00 — 0 commitsSat 23:00 — 0 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.
DateListRankStars gained
Sep 4, 2026monthly#11+15,189
Sep 3, 2026monthly#11+15,189
Sep 2, 2026monthly#6+15,686
Sep 1, 2026monthly#6+15,760
Aug 31, 2026monthly#3+15,913
Aug 30, 2026monthly#4+15,923
Aug 29, 2026monthly#2+15,798
Aug 28, 2026monthly#2+15,653
Aug 27, 2026monthly#2+15,471
Aug 26, 2026monthly#1+15,253
Aug 25, 2026monthly#2+15,093
Aug 24, 2026monthly#2+14,878
Aug 23, 2026monthly#3+14,702
Aug 22, 2026monthly#5+14,568
Aug 21, 2026monthly#5+14,407
  • morluto/rea

    Reverse engineer anything with agents, from app behavior down to native binaries.

    471.6K stars · TypeScript

  • freeCodeCamp/freeCodeCamp

    freeCodeCamp.org's open-source codebase and curriculum. Learn math, programming, and computer science for free.

    459.4K stars · TypeScript

  • openclaw/openclaw

    The AI that really does things. Any OS. Any Platform. The lobster way. 🦞

    394.9K stars · TypeScript

  • affaan-m/ECC

    The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

    307.9K stars · JavaScript

  • NousResearch/hermes-agent

    The agent that grows with you

    265K stars · Python

  • anomalyco/opencode

    The open source coding agent.

    228.3K stars · TypeScript