ReMe/docs/en/quick_start.md
jinliyl ab66f2bb56
docs: refresh ReMe guides, diagrams, and Studio documentation (#447)
* docs: update ReMe documentation URL

* docs: localize ReMe Studio social image

* docs(AGENTS): update agent guidelines and repository documentation structure

- Clarify coding agent guidance for keeping changes small and consistent
- Revise project principle descriptions for clarity and modern terminology
- Expand repository map with detailed component and folder explanations
- Add configuration and CLI usage instructions, including syntax and merging rules
- Elaborate on component, step registration, and application lifecycle processes
- Define jobs, steps, and state handling conventions for stateless design
- Specify workspace and file safety policies, including path restrictions and locking
- Update validation commands and testing environment recommendations
- Clarify coding and test conventions, including style and dependency policies
- Distinguish documentation boundaries and update website content contribution notes
- Reinforce change guardrails to avoid breaking backward compatibility and data loss
- Improve svg diagram formatting and textual details in auto dream and proactive flow image

* style(docs): fix font-family syntax in SVG style definitions

- Correct quotation marks around font-family names in memory-as-file.svg
- Standardize font-family formatting by removing unnecessary quotes in reme-blog-architecture.svg
- Ensure consistent CSS style formatting within SVG files for better rendering fidelity

* docs: add ReMe blog to news

* style(docs): inline svg styles and improve text formatting

- Convert multiline SVG style tags into single-line for compactness in multiple figures
- Remove redundant line breaks in subtitle text elements for consistency
- Shorten descriptive texts in SVG figures for clarity and conciseness
- Adjust font sizes and text for better readability in SVG elements
- Correct whitespace issues in Chinese markdown document for improved formatting
- Remove unused style blocks from framework structure SVG for cleaner code
2026-08-12 10:59:03 +08:00

5.6 KiB

Quick Start

Installation

ReMe requires Python 3.11+.

Install from pip:

pip install "reme-ai[core]"

Install from source:

git clone https://github.com/agentscope-ai/ReMe.git
cd ReMe
pip install -e ".[core]"

Installing the core extra is recommended. The current code imports the AgentScope wrapper, and self-evolving memory also depends on it.

To use agent workflows such as auto_memory, auto_resource, and auto_dream, configure an LLM:

cat > .env <<'EOF'
LLM_BACKEND=openai
LLM_MODEL_NAME=qwen3.7-plus
LLM_API_KEY=your_api_key
LLM_BASE_URL=https://dashscope.aliyuncs.com/compatible-mode/v1
EOF

You can initially omit the LLM configuration if you only need basic file operations and BM25 retrieval.


Start the Service

reme start

The default service address is 127.0.0.1:2333. If the port is already in use:

reme start service.port=8181
reme version
reme health_check
reme help

reme help lists server actions. Ordinary commands invoke server Jobs over HTTP.

When the package includes the web build, open http://127.0.0.1:2333/ for ReMe Studio. It uses the same service to browse, edit, and search the workspace and inspect the digest wikilink graph. Disable it with service.web_enabled=false, or provide a custom build with service.web_static_dir / REME_WEB_STATIC_DIR. The Job API still starts if no web build is found.


Workspace Layout

The default workspace is .reme/ under the current directory. It is created automatically at startup:

.reme/
├── metadata/   # persistent indexes, graph, catalogs, and related state
├── session/    # source conversation records
├── mem_session/ # generated Agent wrapper sessions/config
├── resource/   # external resources
├── daily/      # daily notes
└── digest/     # long-term memory

For directory layers, Markdown frontmatter, and wikilink semantics, see Memory as File.

You can also specify the workspace at startup:

reme start workspace_dir=/tmp/reme-demo service.port=8181

reme write \
  path=digest/wiki/quick-start-demo \
  name="Quick Start Demo" \
  description="Example memory for the quick start" \
  content="# Quick Start Demo

The default live watcher indexes Markdown under the daily and digest directories.

Related link: [[digest/wiki/search-demo.md]]"

path is relative to the workspace. A missing suffix is automatically completed with .md. For Markdown files, name and description are written to frontmatter.

The background watcher builds the index automatically. You can also rebuild it manually:

reme reindex

Search:

reme search query="quick start example memory" limit=5

Read:

reme read path=digest/wiki/quick-start-demo start_line=1 end_line=20

With the default configuration, retrieval is primarily BM25 plus wikilink graph expansion. Vector retrieval is supported by the code, but the embedding store is disabled by default. For the full retrieval flow, see Memory Search.


Files and Daily Notes

reme stat path=digest/wiki/quick-start-demo
reme edit path=digest/wiki/quick-start-demo old="indexes" new="continuously indexes"
reme frontmatter_read path=digest/wiki/quick-start-demo
reme frontmatter_update path=digest/wiki/quick-start-demo metadata='{"tags":["demo"]}'

The file-listing Job can be called directly from the CLI:

reme list path=digest recursive=true limit=50

The equivalent HTTP call is:

curl -s http://127.0.0.1:2333/list \
  -H 'Content-Type: application/json' \
  -d '{"path":"digest","recursive":true,"limit":50}'

Daily notes:

reme write path=daily/2026-06-20/demo-session.md name=demo-session description="Demo session" content="Recorded content"
reme daily_list
reme daily_reindex

write can create a daily note directly. Run daily_reindex when the day's index needs to be refreshed.


Automatic Memory

reme auto_memory \
  session_id=chat-demo \
  messages='[{"role":"user","content":"I prefer to preserve project experience as Markdown."},{"role":"assistant","content":"Recorded."}]' \
  memory_hint="Record the user's preference"

After placing external material under resource/YYYY-MM-DD/ or directly under resource/, the default background task watches md/txt/json/jsonl/csv/yaml/html. You can also trigger processing manually:

reme auto_resource changes='[{"path":"resource/2026-06-20/report.md","change":"added"}]'

Distill daily notes into long-term digest memory:

reme auto_dream date=2026-06-20
reme proactive date=2026-06-20

These flows require a working LLM. Without an LLM configuration, start with basic capabilities such as write, read, and search.

For more detail, see Auto Memory, Auto Resource, Auto Dream, and Proactive.


HTTP and Configuration

Every service-enabled Job is exposed as POST /<job>:

curl -s http://127.0.0.1:2333/version \
  -H 'Content-Type: application/json' \
  -d '{}'

curl -s http://127.0.0.1:2333/search \
  -H 'Content-Type: application/json' \
  -d '{"query":"quick start","limit":5}'

The default configuration comes from reme/config/default.yaml. Override it at startup with dot notation:

reme start \
  workspace_dir=/tmp/reme-demo \
  service.host=127.0.0.1 \
  service.port=8181 \
  enable_logo=false

You can also specify a YAML or JSON configuration file:

reme start config=/path/to/custom.yaml