Source: https://seerepo.com/compare/CherryHQ/cherry-studio/vs/TencentCloud/TencentDB-Agent-Memory
Markdown source: https://seerepo.com/compare/CherryHQ/cherry-studio/vs/TencentCloud/TencentDB-Agent-Memory.md
Description: cherry-studio and TencentDB-Agent-Memory share 17 technologies: Vite, React, SQLite, lru-cache, sqlite-vec, MCP, OpenAI, Anthropic, Tailwind CSS, Drizzle, ai, yaml, officeparser, remark-gfm, Zod, opentelemetry, and docx-preview. Both are written in TypeScript.

# cherry-studio vs TencentDB-Agent-Memory

cherry-studio and TencentDB-Agent-Memory share 17 technologies: Vite, React, SQLite, lru-cache, sqlite-vec, MCP, OpenAI, Anthropic, Tailwind CSS, Drizzle, ai, yaml, officeparser, remark-gfm, Zod, opentelemetry, and docx-preview. Both are written in TypeScript.

- [CherryHQ/cherry-studio](https://seerepo.com/r/CherryHQ/cherry-studio): Your AI workspace for models, agents, and productivity.
- [TencentCloud/TencentDB-Agent-Memory](https://seerepo.com/r/TencentCloud/TencentDB-Agent-Memory): 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.

## What they share and what sets them apart

- In common: Vite, React, SQLite, lru-cache, sqlite-vec, MCP, OpenAI, Anthropic, Tailwind CSS, Drizzle, ai, yaml, officeparser, remark-gfm, Zod, opentelemetry, docx-preview
- Only in cherry-studio: TanStack, dexie, electron-store, @aws-sdk/lib-storage, Sentry, Electron, elysia, @electron-toolkit/preload, quickjs-wasi, grammy, quick-lru, PostCSS, tailwind-merge, tiptap, motion, React Hook Form, react-spinners, @tanstack/react-virtual, react-hotkeys-hook, dnd-kit, react-error-boundary, echarts, @uiw/react-codemirror, xyflow, @floating-ui/dom, virtua, emoji-picker-react, @dagrejs/dagre, @pierre/highlights, @react-aria/live-announcer, ansi-to-react, CodeMirror, react-player, Lucide, ai-sdk, earendil-works, tesseract.js, ollama-ai-provider-v2, partial-json, gpt-tokenizer, unified, streamdown, file-type, unist-util-visit, remark-parse, sharp, markdown-it, qrcode.react, turndown, @firecrawl/anydoc, dompurify, htmlparser2, @napi-rs/canvas, katex, remove-markdown, @mozilla/readability, @tiptap/markdown, Cheerio, docx, fast-xml-parser, gray-matter, html-to-image, html-to-text, mdast-util-from-markdown, mediabunny, micromark-util-types, pdf-lib, pdf-parse, pdfjs-dist, qrcode, remark-math, remark-stringify, word-extractor, @hookform/resolvers, winston, winston-daily-rotate-file, @earendil-works/pi-ai, OpenRouter, @aiden0z/pptx-renderer, exceljs, @ai-sdk/provider-utils, class-variance-authority, Radix UI, uiw, @lezer/highlight, cmdk, react-day-picker, react-dropzone, react-resizable-panels, vaul, rehype-parse, rehype-stringify, remark-github-blockquote-alert
- Only in TencentDB-Agent-Memory: MongoDB, ClickHouse, Redis, Hono, react-router-dom, js-tiktoken, openclaw, node-llama-cpp, @earendil-works/pi-coding-agent, @hono/swagger-ui, @hono/node-server, @langfuse/otel, @opentelemetry/sdk-node, jose, @react-sigma/core, graphology-layout-forceatlas2, react-markdown, xlsx, js-yaml, langfuse

## Side by side

| | cherry-studio | TencentDB-Agent-Memory |
|---|---|---|
| Size | 1,744,076 lines written, 6,114 code files | 260,116 lines written, 978 code files |
| Who writes it | 11.8% of its commits signed by AI. With Claude Code, GitHub Copilot, Cursor, Factory, Jules, Amp, Gemini CLI, Qwen Code, and Codex | 6.9% of its commits signed by AI. With Cursor and Codex |
| Activity | Last push November 5, 2026, 9,918 commits, 53,285 stars | Last push November 4, 2026, 72 commits, 30,616 stars |
| Tests | 3,190 test files. 47.1% of its code files have a test that imports them | 5 test files. 2.2% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, cherry-studio or TencentDB-Agent-Memory?

cherry-studio, with 1,744,076 lines written; TencentDB-Agent-Memory has 260,116.

The proof: [CherryHQ/cherry-studio's code at commit 2292fdd](https://github.com/CherryHQ/cherry-studio/tree/2292fdd739266df12518e4f706de1aa99f66015f)

### Which has more GitHub stars, cherry-studio or TencentDB-Agent-Memory?

cherry-studio, with 53,285 stars; TencentDB-Agent-Memory has 30,616.

The proof: [CherryHQ/cherry-studio on GitHub](https://github.com/CherryHQ/cherry-studio)

### Which has more tests, cherry-studio or TencentDB-Agent-Memory?

cherry-studio, with 3,190 test files; TencentDB-Agent-Memory has 5.

The proof: [CherryHQ/cherry-studio's code at commit 2292fdd](https://github.com/CherryHQ/cherry-studio/tree/2292fdd739266df12518e4f706de1aa99f66015f)

### Which was updated more recently, cherry-studio or TencentDB-Agent-Memory?

cherry-studio: its last push was on November 5, 2026, and TencentDB-Agent-Memory's on November 4, 2026.

The proof: [CherryHQ/cherry-studio's commits on GitHub](https://github.com/CherryHQ/cherry-studio/commits)

### Which has more commits signed by AI, cherry-studio or TencentDB-Agent-Memory?

cherry-studio: an AI signed 11.8% of its commits, with Claude Code, GitHub Copilot, Cursor, Factory, Jules, Amp, Gemini CLI, Qwen Code, and Codex; in TencentDB-Agent-Memory, 6.9%.

The proof: [the commits each tool signed in CherryHQ/cherry-studio](https://seerepo.com/r/CherryHQ/cherry-studio/ai)

## Sources

- CherryHQ/cherry-studio: Read on November 5, 2026, at commit 2292fdd (https://github.com/CherryHQ/cherry-studio/tree/2292fdd739266df12518e4f706de1aa99f66015f)
- TencentCloud/TencentDB-Agent-Memory: Read on November 7, 2026, at commit 2002196 (https://github.com/TencentCloud/TencentDB-Agent-Memory/tree/2002196f2d7c22ea267cfcaf67c5a6fa861df681)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.
