agentscope-ai

ReMe: Build a File-Based Memory Workspace for AI Agents

ReMe is a Python memory-management kit for agents, built around a local-first, self-evolving knowledge base stored as Markdown files. It helps agent users capture conversations and resources, refine durable knowledge, and retrieve relevant context across supported agent integrations.

ActivePythonApache-2.0AI AgentsAgent MemoryLocal First
Stars
3.7k
Forks
321
Stars, last 30 days
+207
Last commit
today
Contributors
39

Our take

Activeregular commits and releases

Health score

68/100

How it is scored
Activity
87
Community
53
Issues
69
Pull requests
64

+207 stars in the last 30 days

  • Merges more pull requests than 94% of the projects we track
  • Releases more often than 90% of the projects we track

ReMe is an actively maintained, Apache-2.0 Python toolkit for teams that want agent memory to remain inspectable and portable as files, rather than hidden in a proprietary store.

Good fit if

  • You want durable Markdown memory shared across agents, with local workspace files as the source of truth.
  • Your workflow benefits from conversation capture, knowledge consolidation, and BM25 retrieval without requiring embeddings by default.
  • You can use Python 3.11+ and want to connect through a CLI, service, MCP, or a listed agent integration.

Look elsewhere if

  • You need a fully managed hosted memory service rather than a workspace and service you operate.
  • You require semantic vector retrieval without configuring and enabling an embedding component.
  • Your agent runtime cannot use ReMe’s CLI, HTTP, MCP, Python API, or an available integration.
All health signals
Last commit2026-10-22 (today)
Commits, last 90 days100+
Releases, last 12 months77 (latest v0.4.1.13, 2026-10-04)
Contributors39 (top contributor: 73% of commits)
Issues closed, last 90 days15+ (typically closed in 2 days)
Pull requests merged, last 90 days92 (typically merged in 1 day)
Project age2 years

Checked on 2026-10-23 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

3,785

Forks

348

Change since Nov 10, 2026: +6 stars·+2 forks

Overview

ReMe is a Python memory-management kit for AI agents, built around a local-first, self-evolving personal knowledge base whose durable memory is ordinary Markdown. It addresses the gap between short-lived conversations and useful long-term context: agents can capture conversations and resources, progressively refine them into knowledge, and retrieve relevant passages without loading the whole workspace into context.

The same workspace can serve personal assistants and coding agents through the CLI, HTTP, MCP, Python APIs, and integrations for QwenPaw, DeepSeek Harness, OpenClaw, Claude Code, Hermes, and Codex. ReMe combines BM25 search with optional embeddings and wikilink expansion; embeddings are disabled by default.

Key Features

  • Stores durable memory in editable Markdown files with frontmatter and wikilinks, while keeping indexes and metadata rebuildable.
  • Captures conversation records and distills useful information into daily memory cards.
  • Imports external resources into source-linked daily cards, including image resources.
  • Consolidates daily notes into long-term knowledge and procedural memory through Auto Dream.
  • Searches at passage level with BM25, wikilink expansion, and optional embedding-based retrieval.
  • Offers workspace operations through a CLI, HTTP service, MCP server, Studio interface, and Python API.
  • Supports integrations that add recall and memory capture to agent workflows.

Use Cases

  • Personal assistant users can accumulate preferences, facts, and recurring context across conversations while retaining direct control of the files.
  • Coding-agent users can preserve project procedures and prior decisions for retrieval in later sessions.
  • Researchers can turn reference materials into linked, searchable notes alongside conversation-derived knowledge.
  • Agent developers can add shared memory to supported runtimes through ReMe’s service interfaces or Python API.

What you need

Detected in the repository

  • Python >=3.11 (from pyproject.toml)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • A test suite and automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install the core package with Python 3.11 or newer, then start the service:

pip install "reme-ai[core]"
reme start

See the README for workspace setup, configuration, Docker deployment, and agent integrations.

Alternatives

  • EverOS: EverOS focuses on persistent conversation memory in editable Markdown, while ReMe also captures resources and refines durable knowledge.
  • memoripy: Memoripy tracks changing facts with evidence screening and cited recall, rather than centering a Markdown knowledge base.
  • OpenViking: OpenViking organizes agent context in a browsable virtual filesystem and supports hosted use, while ReMe centers on local Markdown files.
  • cabinet: Cabinet adds scheduled jobs and team workflows to its Markdown knowledge base, beyond ReMe's agent memory-management focus.
ProjectLanguageLicenseStarsStatus
ReMePythonApache-2.03.7kActive
EverOSPythonApache-2.013.4kActive
memoripyPythonApache-2.0694Active
OpenVikingPythonAGPL-3.039.2kActive
cabinetTypeScriptMIT2.9kActive

Considerations

  • The project is active, with regular commits and releases, and its recent issue and pull-request handling has been brisk. Its contributor base is distributed rather than dominated by one person, but the feature set and integrations are substantial, so evaluate the specific workflows your deployment needs.
  • Python 3.11 or newer is required. Docker and Compose are also supported; the README does not specify a GPU requirement.
  • Basic file operations and BM25 search can work without model credentials. LLM credentials are needed for memory evolution workflows, while embedding retrieval requires separately enabling embedding components and configuring an embedding API.
  • ReMe’s durable workspace files are user-managed, but the service and integrations still need to be configured for your environment. Review the deployment and security guidance before exposing the service beyond its intended boundary.
  • The Apache-2.0 license permits broad use, subject to its license terms and notices.

Found this useful?

Share it with someone who would like ReMe.

Comparisons