feat(mem0): self-hosted dashboard backend + recall tuning (salvage #55614) - #762
Open
hashbender wants to merge 1 commit into
Open
feat(mem0): self-hosted dashboard backend + recall tuning (salvage #55614)#762hashbender wants to merge 1 commit into
hashbender wants to merge 1 commit into
Conversation
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
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
The mem0 plugin can now connect to a self-hosted Mem0 dashboard server (the Dockerized FastAPI server), closing the gap between OSS (in-process SDK) and Platform (cloud) modes.
Changes
_backend.py: newSelfHostedBackend— direct httpx client for a self-hosted Mem0 server (X-API-Keyauth,POST /search,GET/POST /memories,PUT/DELETE /memories/{id}), reusing the shared_unwrap_results.get_allreports the true stored total, not the page size (SelfHostedBackend.get_all() returns incorrect count when memories exceed server page limit NousResearch/hermes-agent#52921).__init__.py: route toSelfHostedBackendwhenhostis set (MEM0_HOST/mem0.json); precedence isoss > host > platform. Config schema +is_available()accept host-only (AUTH_DISABLED servers).rerankdefaults tofalse(opt-in viarerank=true, platform only); themem0_listtool is removed (5→4 tools); search guidance is de-shouted.plugin.yaml:1.2.0→1.3.0;mem0ai>=2.0.10,<3.Maintainer follow-ups on top of the salvage
Two sibling surfaces didn't mirror the new
oss > host > platformrouting precedence added to_create_backend:system_prompt_block()checkedhostbeforeoss, so anoss+hostconfig ran OSS but told the model it was self-hosted HTTP. Reordered to match routing.hermes memory setup mem0 --mode platformleft a stalehostinmem0.json; sincehostbeatsplatform, the user kept routing to the self-hosted server.save_configmerges (no key deletion), sohostis now cleared to""(overwrites on merge, reads falsy) rather than popped.Authorization: ***docstring artifact.Validation
Salvage of NousResearch#55614 by @kartik-mem0 (mem0 maintainer) — cherry-picked to preserve authorship, with the sibling-surface follow-ups above. Also supersedes the self-hosted portion of NousResearch#52487 by @liuhao1024 (first-submitted independent implementation of the same
SelfHostedBackend) — credited.Closes NousResearch#52478
Fixes NousResearch#52921
Mirror-of: NousResearch#56943
NousResearch#56943