agent-beacon vs TencentDB-Agent-Memory
Cross-harness memory for coding agents: captures sessions from Claude Code, Cursor, Codex and 20+ harnesses, distills reviewed knowledge over MCP/skills, and forwards telemetry to SIEMs. — versus — Tencent's team memory hub for agents: an API proxy turns conversations, docs and code into shared chat memory, skills, an LLM wiki and a code graph, reused across agents.
Both give memory across many coding agents. agent-beacon captures sessions locally; TencentDB intercepts at a proxy and shares across a team.
| agent-beacon | TencentDB-Agent-Memory | |
|---|---|---|
| Stars | 3.3k | 31k |
| Forks | 291 | 3.0k |
| Language | Go | TypeScript |
| License | MIT | NOASSERTION |
| Last activity | yesterday | 2 days ago |
| Topics | memory, coding, security | memory, gateway |
| Curated connections | 4 | 4 |
agent-beacon — the curator's take
Two jobs in one endpoint agent, and it pays to know which one you want. The memory side captures every session across Claude Code, Codex, Cursor, OpenCode and 20+ harnesses, replays them exactly, and turns fixes and conventions into reviewed knowledge future agents pull through MCP or Agent Skills. The security side normalizes the same traces into an OpenTelemetry event model and ships them to Splunk, Sentinel, CrowdStrike LogScale and friends, with MSI, .deb/.rpm and MDM installs. Strong fit when a team runs many harnesses and wants one record for both recall and audit. Watch the default: interactive setup preselects hosted Beacon Managed forwarding (Local is an explicit opt-out), so choose deliberately on machines with sensitive code. For solo, single-harness recall, claude-mem or deja-vu is less machinery.
TencentDB-Agent-Memory — the curator's take
Use it when a team wants every agent (Claude Code, CodeBuddy, others) to share governed memory with zero integration: point the base URL at its proxy and memory is captured. Skip it if routing all LLM traffic through a proxy is unacceptable, or for a single developer: it runs three services and needs two LLM configs. Team Memory is in beta and the MongoDB backend is experimental; the license is custom.