RRepoGEO

REPOGEO REPORT · LITE

ClaudioDrews/memory-os

Default branch main · commit 4b386e37 · scanned 6/7/2026, 10:43:09 AM

GitHub: 970 stars · 92 forks

AI VISIBILITY SCORE
28 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface ClaudioDrews/memory-os, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition README H1 to clarify AI agent focus

    Why:

    CURRENT
    # Memory OS — Hermes Agent Memory Operating System
    COPY-PASTE FIX
    # Memory OS: Persistent Memory & Context Management for AI Agents
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://github.com/ClaudioDrews/memory-os
  • mediumreadme#3
    Emphasize project maturity in the README introduction

    Why:

    COPY-PASTE FIX
    Add this sentence to the introductory section of the README: "Developed for robust, production-ready AI agent collaboration, Memory OS is actively maintained with community contributions and systematic audits."

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface ClaudioDrews/memory-os
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
weaviate/weaviate
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. weaviate/weaviate · recommended 1×
  2. qdrant/qdrant · recommended 1×
  3. pgvector/pgvector · recommended 1×
  4. chroma-core/chroma · recommended 1×
  5. milvus-io/milvus · recommended 1×
  • CATEGORY QUERY
    Seeking a self-hosted solution for AI agent long-term memory and context management.
    you: not recommended
    AI recommended (in order):
    1. Weaviate (weaviate/weaviate)
    2. Qdrant (qdrant/qdrant)
    3. PostgreSQL with pgvector (pgvector/pgvector)
    4. Chroma (chroma-core/chroma)
    5. Milvus (milvus-io/milvus)
    6. Redis with Redis Stack (RediSearch/RedisJSON) (RedisLabs/RedisStack)

    AI recommended 6 alternatives but never named ClaudioDrews/memory-os. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What open-source tools provide intelligent context injection and RAG for local LLMs?
    you: not recommended
    AI recommended (in order):
    1. LlamaIndex
    2. LangChain
    3. Haystack (deepset/Haystack)
    4. FAISS
    5. Chroma
    6. Weaviate

    AI recommended 6 alternatives but never named ClaudioDrews/memory-os. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of ClaudioDrews/memory-os?
    pass
    AI named ClaudioDrews/memory-os explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts ClaudioDrews/memory-os in production, what risks or prerequisites should they evaluate first?
    pass
    AI named ClaudioDrews/memory-os explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo ClaudioDrews/memory-os solve, and who is the primary audience?
    pass
    AI did not name ClaudioDrews/memory-os — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of ClaudioDrews/memory-os. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/ClaudioDrews/memory-os.svg)](https://repogeo.com/en/r/ClaudioDrews/memory-os)
HTML
<a href="https://repogeo.com/en/r/ClaudioDrews/memory-os"><img src="https://repogeo.com/badge/ClaudioDrews/memory-os.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

ClaudioDrews/memory-os — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite