Long-term collaborative memory for workplace agents.
MemWing gives workplace agents a governable memory layer: capture Source Events, build Current Truth, surface project context, manage memory lifecycle, and push timely reminders back into collaboration flows.
Quickstart | Control Plane | Runtime Profiles | Architecture | CLI | License | 中文
Most workplace agents are clever but forgetful. They can answer the current prompt, but lose the thread across project decisions, Lark discussions, tool runs, shifting deadlines, and "we already decided this last week" moments.
MemWing is a long-term collaborative memory system for those agents. It stores authoritative Source Events, derives recallable memory layers, tracks what is current versus historical, and gives humans a Control Plane for review, redaction, lifecycle changes, and proactive push.
It is built for teams that need memory to be useful, explainable, and governable.
The happy path is designed to feel like installing a normal local tool.
brew install memwing
memwing quickstartPrefer an install script?
curl -fsSL https://raw.githubusercontent.com/GaosCode/MemWing/main/packaging/install.sh | sh
memwing quickstartmemwing quickstart uses the Lite profile by default. It creates local state,
links the OpenClaw plugin, configures the context engine, and starts the MemWing
runtime.
memwing status
memwing doctorMemWing is not only a memory API. It includes a Control Plane for humans to inspect and govern what agents remember.
memwing control-planeUse the Control Plane to:
- review Memory Items before they become trusted long-term context
- inspect Source Events behind an answer or push candidate
- approve, archive, redact, or purge memory with a reason
- monitor Page Memory, pipeline readiness, and maintenance queues
- send proactive memory cards back into workplace collaboration flows
| Profile | Best For | Storage | Derived Backends | Setup |
|---|---|---|---|---|
| Lite | personal trials, demos, OpenClaw users who do not want databases | SQLite | graph and evidence disabled | memwing quickstart |
| Full Local | local evaluation with full retrieval stack | Postgres | Qdrant + Neo4j / Graphiti | memwing quickstart --profile full-local |
| Production | managed infrastructure for teams | Postgres | managed Qdrant + Neo4j / Graphiti | memwing setup --profile production |
Lite is intentionally close to consumer software: no Docker, no Postgres, no Qdrant, no Neo4j, and no separate model credentials. By default, model calls go through the agent runtime.
MemWing is platform-neutral, but today it has a first-class OpenClaw path and workplace collaboration flows designed around Lark.
With OpenClaw, MemWing provides:
- a ContextEngine for context assembly, after-turn capture, and compaction
- conversation hooks for Source Event capture
- tools for memory search, source lookup, project context, and explanation
- native-memory compatibility shims for agent workflows
With Lark-style workplace flows, MemWing is designed to remember:
- project decisions and their reasons
- changing preferences and deadlines
- recurring team workflows
- information that should be resurfaced before it is forgotten
Core vocabulary:
- Source Event: the authoritative raw collaboration event.
- Current Truth: the effective fact set preferred at recall time.
- Page Memory: editable mid-term project or thread summary.
- Memory Item: governable long-term memory with lifecycle state.
- Evidence Index: derived retrieval layer over Source Events.
- Graph Backend: entity and relationship layer for validity and history.
- Control Plane: human governance surface for memory review and operations.
# One-command local setup
memwing quickstart
# Start runtime from existing config
memwing start
# Inspect local configuration and health
memwing status
memwing doctor
# Open the memory governance UI
memwing control-plane
# Install or inspect the OpenClaw plugin
memwing openclaw install
memwing openclaw status
# Production config skeleton
memwing setup --profile productionAutomation and scripts can also call the Control API through the low-level
memwing control ... command family.
Backend setup:
uv sync
uv run pytest
uv run ruff check .Run the backend locally:
# Start API and Memory Pipeline Runtime together
uv run memwing-runtime
# Or run the entrypoints separately
uv run memwing-api
uv run memwing-pipelineCLI development:
uv run memwing quickstart --skip-openclaw --no-start
uv run memwing status --no-health
uv run memwing doctor --jsonControl Plane frontend:
cd frontend
npm install
npm run devOpenClaw plugin development:
cd memwing/integrations/openclaw
npm install
npm run build
npm run smokeMemWing is evolving quickly. The current implementation focuses on the v1 memory runtime, OpenClaw integration, Lite setup, Control Plane APIs, benchmark support, and local-first developer workflows.
MemWing is released under the Apache License 2.0. See the root LICENSE file
for the full license text.