Poll PositionLook before you build

Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.

ReMe (formerly MemoryScope)

From Alibaba's AgentScope team: local-first, file-based memory kit that stores agent memory as Markdown with frontmatter and wikilinks, shared across agents via CLI, HTTP, MCP and plugins.

reme.agentscope.io/Changed direction

modelscope/MemoryScope now redirects to agentscope-ai/ReMe (MemoryScope kept on memoryscope_branch; last memoryscope PyPI 0.1.1.0 2024-09-11). ReMe v0.4.1.13 released 2026-10-04; pushed 2026-10-23. (checked 2026-10-25)

In Agent memory

Where it stands apart

What it shares with most of the community

Nearest neighbors

Every answer

QuestionAnswerSource
Is it actively maintained?active
Active after pivoting from MemoryScope's design to 'memory as file'.
source
2026-10-25
How is the main thing licensed?permissive open source (MIT/Apache/BSD)
Apache-2.0
source
2026-10-25
How is it mainly sustained?stands apart big company side project
AgentScope (Alibaba/ModelScope ecosystem).
source
2026-10-25
Can it run entirely on your own device or infrastructure, without the maker's servers?yessource
2026-10-25
Do you need an account to use it?no account
Local file-based; no account mentioned, only optional LLM/embedding API keys.
source
2026-10-26
Who is it for?developerssource
2026-10-25
Which shared standard or format does it mainly build on?stands apart plain Markdown files (wikilinks, frontmatter)
Markdown with frontmatter and wikilinks.
source
2026-10-26
In the default setup, who mainly decides what gets remembered?the system, by extracting memories from conversations or data in the background
Automatic turn capture and scheduled 'Auto Dream'; agents also get search tools.
source
2026-10-25
How can the person the memories are about see and edit them?directly, as readable files or in a UI they control
'readable, editable' Markdown; users retain control of the files.
source
2026-10-25
By default, how do old or wrong memories mainly go away?the system updates, merges, or decays them automatically
Self-evolving workflows and scheduled consolidation.
source
2026-10-25
Where do memories live in the default setup the docs lead with?stands apart on the end user's own devicesource
2026-10-25
Does it work with models from different LLM vendors?yes, model-agnosticsource
2026-10-25
What is the main storage model for long-term memory?stands apart plain files (Markdown, text, JSON)source
2026-10-25
What shape does it mainly take (the one its docs lead with)?memory service (self-hosted server or hosted API)source
2026-10-25
Is there a first-party MCP server for it?yessource
2026-10-25
How is memory separated between users or tenants?one store per user or agent; the app partitions it
One shared memory workspace across agents.
source
2026-10-25
Does it publish scores on public memory benchmarks (LoCoMo, LongMemEval, BEAM, etc.)?yes
LongMemEval 89.4%, BEAM.
source
2026-10-25

Sources

This page was derived from:

RSS for this project

Are you a maintainer? Claiming and correcting projects is coming soon.