Skip to main content
Drop a repoSign up
NEWvicrodh/qbzjust droppedNEWkowalski-ptr/compass-before-compactjust droppedNEWlastmile-ai/mcp-agentjust droppedREPOstablyai/orca+328 stars 24hREPOdiegosouzapw/OmniRoute+251 stars 24hREPOpbakaus/impeccable+205 stars 24hREPOkoala73/worldmonitor+178 stars 24hREPOsafishamsi/graphify+169 stars 24hNEWvicrodh/qbzjust droppedNEWkowalski-ptr/compass-before-compactjust droppedNEWlastmile-ai/mcp-agentjust droppedREPOstablyai/orca+328 stars 24hREPOdiegosouzapw/OmniRoute+251 stars 24hREPOpbakaus/impeccable+205 stars 24hREPOkoala73/worldmonitor+178 stars 24hREPOsafishamsi/graphify+169 stars 24h
mem0ai/mem0publicTypeScriptgithub.com/mem0ai/mem0
mem0ai avatar

mem0

Universal memory layer for AI Agents

AGENT MEMORYAI AGENTSLLM INFRAAICHATGPTLLMTRENDING #130

// OWNER · mem0ai · REPO SNAPSHOT

github.com/mem0ai

mem0ai

Universal memory layer for AI Agents

STARS61,788+474 · 7d
FORKS7,202+0 · 7d
CONTRIBUTORS0maintainer graph thin
OPEN ISSUES · PRS220· 0 
LICENSEno license file
LANGUAGETypeScript 
FOUNDED
LOCATION
MEMBERS
PUBLIC REPOS
TOTAL STARS
FOCUS
FUNDING

//STAR HISTORY · 12M

+3,471 all-time-window
Stars · cumulative61,793 · today
//WHY IT'S TRENDING· expert verdict · 35% confidence

open-source memory layer for LLM applications with persistent user context

mem0ai/mem0 is a memory infrastructure project for AI agents that has surfaced strongly on dev.to (rank 8) but lacks broader cross-platform signal. Our pipeline flagged it at rank 70 before external feeds, yet only 1 of 8 weighted sources shows meaningful activity, making this a thin early call in a pool where 83.5% of entities are single-source noise.

Why now: LLM memory/retention is a hot infrastructure problem as agents move beyond stateless chat; dev.to community may be early to tutorial content before broader developer adoption.

  • Only dev.to (rank 8) shows signal; zero presence on GitHub, Hacker News, X/Twitter, Reddit, Product Hunt, Bluesky despite those sources having 100-1000 rows in pool
  • Source count of 1 with 8 weighted sources available indicates severe confirmation gap
  • Pool context: 167/200 entities are single-source; early_call band has 18 entries but this is one of the weakest by source coverage
  • External rank 156 vs ours 70 shows no external validation gap—external feeds simply haven't found it

Considerations: Single-source signals on dev.to are easily gamed through cross-posting or small-community upvotes. No GitHub velocity, no HN discussion, no X traction means developers aren't actually building with it yet. Memory layers for LLMs are a crowded space (LangChain memory, Zep, Chroma) and differentiation is unproven. High hype risk from 'AI infrastructure' framing without usage evidence.

EMERGING SIGNAL · Watch: Monitor for GitHub star velocity or HN/Reddit mention in next 14 days; if no second-source confirmation emerges, deprioritize as dev.to content bubble.

Sources: dev.to search: mem0ai/mem0

↻ refreshed 24m ago· next sync in 41m· sourced from 1 channel · 11 mentions / 24h

Methodology: synthesized from this project's own documentation, live GitHub data, third-party coverage, and multi-platform signal convergence — by AISO.tools.

FAQ · answers from the data spine

What is mem0ai/mem0?
Universal memory layer for AI Agents
Who maintains mem0?
Maintained by mem0ai (the owner) on GitHub.
What language is mem0 written in?
Primarily TypeScript.
When was mem0 created? When was the last update?
Created June 20, 2023 · last commit July 25, 2026.
How do I install mem0?
Clone the repo:
git clone https://github.com/mem0ai/mem0.git
Then follow the README in the cloned directory.
Is mem0 actively maintained?
stalled — no commits for an extended period

//COMMENTS · 0

live thread · operators only

Sign in to join the discussion

Be the first to comment.
Created
Updated
Last commit
Repositorymem0ai/mem0