Add mem0ai/mem0 to Memory & Context#79
Merged
ksimback merged 1 commit intoksimback:mainfrom May 1, 2026
Merged
Conversation
|
@liviaellen is attempting to deploy a commit to the Kevin's projects Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced Apr 24, 2026
ksimback
added a commit
that referenced
this pull request
Apr 25, 2026
validate-repo-suggestion.yml read repos.json from the workflow's local checkout, then committed that content to a branch based on latest main. If any other PR merged to main between checkout and this step (concurrent auto-PR, manual merge, bot push), the local copy was stale — and the later squash-merge silently dropped everything that had landed in the gap. Surfaced by PR #89: keepnotes-ai/keep was added cleanly, but AxDSan/mnemosyne (added by PR #88 during the gap) was overwritten and had to be restored later in PR #94. PR #79 (mem0) is still DIRTY for the same reason and needs manual rebase or workflow re-trigger. Fix: fetch repos.json content via the GitHub API (`ref: 'main'`) right before mutating it, instead of reading from `fs`. The fetched `file.sha` is then used as the parent SHA for createOrUpdateFileContents — same optimistic-concurrency check as before, so if another PR squeaks in between the fetch and the commit, this one fails loudly with a 409 instead of silently dropping content. Removed: the now-redundant second `getContent` call and the unused `require('fs')`. Co-authored-by: Kevin Simback <16635828+ksimback@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
mem0 is a universal memory layer shipped as an official Hermes Agent memory provider (one-command setup via `hermes memory setup`). Adds the repo to the Memory & Context category on the map and the best-memory-providers list, with a gbrain-style overview summarizing the three auto-invoked tools (mem0_profile, mem0_search, mem0_conclude) and the non-blocking, circuit-breakered retrieval model. Also calls out the OSS / self-hosted path: mem0 is Apache-2.0, so the same provider runs either managed (app.mem0.ai) or fully self-hosted via the Python SDK (`pip install mem0ai`) or Docker Compose stack (Postgres + Qdrant + your own LLM/embedder), pointing Hermes at a local endpoint. Rebased onto latest main to fix the stale-checkout drift flagged by PR ksimback#112 — earlier branch state had silently dropped contributions from PRs ksimback#74, ksimback#80, ksimback#84, ksimback#87, ksimback#88, ksimback#89 plus the ksimback#105–ksimback#114 fixes.
ellenlivia-mem0
force-pushed
the
add-mem0-memory-provider
branch
from
33579ac to
0df9037
Compare
Author
|
@ksimback adding a rebased to update with new main, so its not dirty + following new base based on recent update. |
3 tasks
ksimback
added a commit
that referenced
this pull request
May 1, 2026
The Web3CZ user account no longer exists on GitHub (HTTP 404 on both the repo and the user). PR #107's fail-loud GraphQL handling correctly surfaced this — build-pages.yml has been failing for at least 2 days (4/30 daily cron + every merge-triggered run since) because lib/github.js throws on the NOT_FOUND, blocking the entire 112-repo metadata fetch. Removing the entry unblocks the rebuild. As of this commit, all 12 new repos added during today's triage (PRs #79, #146, #147) will start appearing on hermesatlas.com. Should also kick off a periodic dead-repo detector so this doesn't recur silently — left as a follow-up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hermes memory setupcommand wires it in, no code changes required. (see here for reference)app.mem0.ai) or self-hosted viapip install mem0aior the Docker Compose stack (Postgres + Qdrant + your own LLM), pointing Hermes at a local endpoint.Files changed
data/repos.json— new Memory & Context entry (53,915 ★, Apache-2.0, Python).data/summaries.json— gbrain-style overview + 4 highlights (managed setup, three auto-invoked tools, non-blocking design, OSS self-host) for the/projects/mem0ai/mem0page.data/list-summaries.json— paragraph for the/lists/best-memory-providersbreakdown, including the OSS deployment option.index.html— new top row in the Memory & Context section (mem0 out-stars the rest); category count bumped 8 → 9.The project HTML and list HTML will be regenerated by
scripts/build-pages.json CI.Links
Test plan
node -e "JSON.parse(...)"on all three edited JSON files — parses clean.index.htmlcount reflects 9 entries in the Memory & Context section.projects/mem0ai/mem0.htmlandlists/best-memory-providers.htmlviascripts/build-pages.js.