Skip to main content

AI Memory and Conversation Management Framework - Simple as mem0, Powerful as MemU

Project description

MemU Banner

memU

Always-On Proactive Memory for AI Agents

PyPI version License: Apache 2.0 Python 3.13+ Discord Twitter

NevaMind-AI%2FmemU | Trendshift

English | 中文 | 日本語 | 한국어 | Español | Français


memU is a memory framework built for 24/7 proactive agents. It is designed for long-running use and greatly reduces the LLM token cost of keeping agents always online, making always-on, evolving agents practical in production systems. memU continuously captures and understands user intent. Even without a command, the agent can tell what you are about to do and act on it by itself.

check our memU bot


⭐️ Star the repository

If you find memU useful or interesting, a GitHub Star ⭐️ would be greatly appreciated.

✨ Core Features

Capability Description
🤖 24/7 Proactive Agent Always-on memory agent that works continuously in the background—never sleeps, never forgets
🎯 User Intention Capture Understands and remembers user goals, preferences, and context across sessions automatically
💰 Cost Efficient Reduces long-running token costs by caching insights and avoiding redundant LLM calls

🔄 How Proactive Memory Works

cd examples/proactive
python proactive.py

Proactive Memory Lifecycle

┌─────────────────────────────────────────────────┐
│  1. USER INITIAL QUERY                          │
│  └─ User input, context, or any trigger event   │
│     Conversation starts here                    │
└─────────────────────────────────────────────────┘
                      ↓
    ┌─────────────────────────────────────────────────┐
    │  2. AGENT PLANNING / ACTIONS                    │
    │  └─ Analyze request, execute tasks              │
    │     Retrieve relevant memories for context      │
    └─────────────────────────────────────────────────┘
                          ↓
    ┌─────────────────────────────────────────────────┐
    │  3. MEMORIZE & UPDATE TODOLIST                  │
    │  └─ Store new insights, facts, preferences      │
    │     Modify task list based on progress          │
    └─────────────────────────────────────────────────┘
                          ↓
    ┌─────────────────────────────────────────────────┐
    │  4. PREDICT USER INTENT                         │
    │  └─ Anticipate next steps and needs             │
    │     Proactively prepare relevant context        │
    └─────────────────────────────────────────────────┘
                          ↓
    ┌─────────────────────────────────────────────────┐
    │  5. LOOP (2 → 4)                                │
    │  └─ Continuous iteration until task complete    │
    │     Agent-driven proactive workflow             │
    └─────────────────────────────────────────────────┘

🎯 Proactive Use Cases

1. Information Recommendation

Agent monitors interests and proactively surfaces relevant content

# User has been researching AI topics
MemU tracks: reading history, saved articles, search queries

# When new content arrives:
Agent: "I found 3 new papers on RAG optimization that align with
        your recent research on retrieval systems. One author
        (Dr. Chen) you've cited before published yesterday."

# Proactive behaviors:
- Learns topic preferences from browsing patterns
- Tracks author/source credibility preferences
- Filters noise based on engagement history
- Times recommendations for optimal attention

2. Email Management

Agent learns communication patterns and handles routine correspondence

# MemU observes email patterns over time:
- Response templates for common scenarios
- Priority contacts and urgent keywords
- Scheduling preferences and availability
- Writing style and tone variations

# Proactive email assistance:
Agent: "You have 12 new emails. I've drafted responses for 3 routine
        requests and flagged 2 urgent items from your priority contacts.
        Should I also reschedule tomorrow's meeting based on the
        conflict John mentioned?"

# Autonomous actions:
 Draft context-aware replies
 Categorize and prioritize inbox
 Detect scheduling conflicts
 Summarize long threads with key decisions

3. Trading & Financial Monitoring

Agent tracks market context and user investment behavior

# MemU learns trading preferences:
- Risk tolerance from historical decisions
- Preferred sectors and asset classes
- Response patterns to market events
- Portfolio rebalancing triggers

# Proactive alerts:
Agent: "NVDA dropped 5% in after-hours trading. Based on your past
        behavior, you typically buy tech dips above 3%. Your current
        allocation allows for $2,000 additional exposure while
        maintaining your 70/30 equity-bond target."

# Continuous monitoring:
- Track price alerts tied to user-defined thresholds
- Correlate news events with portfolio impact
- Learn from executed vs. ignored recommendations
- Anticipate tax-loss harvesting opportunities

...


🗂️ Hierarchical Memory Architecture

MemU's three-layer system enables both reactive queries and proactive context loading:

structure
Layer Reactive Use Proactive Use
Resource Direct access to original data Background monitoring for new patterns
Item Targeted fact retrieval Real-time extraction from ongoing interactions
Category Summary-level overview Automatic context assembly for anticipation

Proactive Benefits:

  • Auto-categorization: New memories self-organize into topics
  • Pattern Detection: System identifies recurring themes
  • Context Prediction: Anticipates what information will be needed next

🚀 Quick Start

Option 1: Cloud Version

Experience proactive memory instantly:

👉 memu.so - Hosted service with 7×24 continuous learning

For enterprise deployment with custom proactive workflows, contact info@nevamind.ai

Cloud API (v3)

Base URL https://api.memu.so
Auth Authorization: Bearer YOUR_API_KEY
Method Endpoint Description
POST /api/v3/memory/memorize Register continuous learning task
GET /api/v3/memory/memorize/status/{task_id} Check real-time processing status
POST /api/v3/memory/categories List auto-generated categories
POST /api/v3/memory/retrieve Query memory (supports proactive context loading)

📚 Full API Documentation


Option 2: Self-Hosted

Installation

pip install -e .

Basic Example

Requirements: Python 3.13+ and an OpenAI API key

Test Continuous Learning (in-memory):

export OPENAI_API_KEY=your_api_key
cd tests
python test_inmemory.py

Test with Persistent Storage (PostgreSQL):

# Start PostgreSQL with pgvector
docker run -d \
  --name memu-postgres \
  -e POSTGRES_USER=postgres \
  -e POSTGRES_PASSWORD=postgres \
  -e POSTGRES_DB=memu \
  -p 5432:5432 \
  pgvector/pgvector:pg16

# Run continuous learning test
export OPENAI_API_KEY=your_api_key
cd tests
python test_postgres.py

Both examples demonstrate proactive memory workflows:

  1. Continuous Ingestion: Process multiple files sequentially
  2. Auto-Extraction: Immediate memory creation
  3. Proactive Retrieval: Context-aware memory surfacing

See tests/test_inmemory.py and tests/test_postgres.py for implementation details.


Custom LLM and Embedding Providers

MemU supports custom LLM and embedding providers beyond OpenAI. Configure them via llm_profiles:

from memu import MemUService

service = MemUService(
    llm_profiles={
        # Default profile for LLM operations
        "default": {
            "base_url": "https://dashscope.aliyuncs.com/compatible-mode/v1",
            "api_key": "your_api_key",
            "chat_model": "qwen3-max",
            "client_backend": "sdk"  # "sdk" or "http"
        },
        # Separate profile for embeddings
        "embedding": {
            "base_url": "https://api.voyageai.com/v1",
            "api_key": "your_voyage_api_key",
            "embed_model": "voyage-3.5-lite"
        }
    },
    # ... other configuration
)

OpenRouter Integration

MemU supports OpenRouter as a model provider, giving you access to multiple LLM providers through a single API.

Configuration

from memu import MemoryService

service = MemoryService(
    llm_profiles={
        "default": {
            "provider": "openrouter",
            "client_backend": "httpx",
            "base_url": "https://openrouter.ai",
            "api_key": "your_openrouter_api_key",
            "chat_model": "anthropic/claude-3.5-sonnet",  # Any OpenRouter model
            "embed_model": "openai/text-embedding-3-small",  # Embedding model
        },
    },
    database_config={
        "metadata_store": {"provider": "inmemory"},
    },
)

Environment Variables

Variable Description
OPENROUTER_API_KEY Your OpenRouter API key from openrouter.ai/keys

Supported Features

Feature Status Notes
Chat Completions Supported Works with any OpenRouter chat model
Embeddings Supported Use OpenAI embedding models via OpenRouter
Vision Supported Use vision-capable models (e.g., openai/gpt-4o)

Running OpenRouter Tests

export OPENROUTER_API_KEY=your_api_key

# Full workflow test (memorize + retrieve)
python tests/test_openrouter.py

# Embedding-specific tests
python tests/test_openrouter_embedding.py

# Vision-specific tests
python tests/test_openrouter_vision.py

See examples/example_4_openrouter_memory.py for a complete working example.


📖 Core APIs

memorize() - Continuous Learning Pipeline

Processes inputs in real-time and immediately updates memory:

memorize ```python result = await service.memorize( resource_url="path/to/file.json", # File path or URL modality="conversation", # conversation | document | image | video | audio user={"user_id": "123"} # Optional: scope to a user )

Returns immediately with extracted memory:

{ "resource": {...}, # Stored resource metadata "items": [...], # Extracted memory items (available instantly) "categories": [...] # Auto-updated category structure }


**Proactive Features:**
- Zero-delay processing—memories available immediately
- Automatic categorization without manual tagging
- Cross-reference with existing memories for pattern detection

### `retrieve()` - Dual-Mode Intelligence

MemU supports both **proactive context loading** and **reactive querying**:

<img width="100%" alt="retrieve" src="assets/retrieve.png" />

#### RAG-based Retrieval (`method="rag"`)

Fast **proactive context assembly** using embeddings:

- ✅ **Instant context**: Sub-second memory surfacing
- ✅ **Background monitoring**: Can run continuously without LLM costs
- ✅ **Similarity scoring**: Identifies most relevant memories automatically

#### LLM-based Retrieval (`method="llm"`)

Deep **anticipatory reasoning** for complex contexts:

- ✅ **Intent prediction**: LLM infers what user needs before they ask
- ✅ **Query evolution**: Automatically refines search as context develops
- ✅ **Early termination**: Stops when sufficient context is gathered

#### Comparison

| Aspect | RAG (Fast Context) | LLM (Deep Reasoning) |
|--------|-------------------|---------------------|
| **Speed** | ⚡ Milliseconds | 🐢 Seconds |
| **Cost** | 💰 Embedding only | 💰💰 LLM inference |
| **Proactive use** | Continuous monitoring | Triggered context loading |
| **Best for** | Real-time suggestions | Complex anticipation |

#### Usage
```python
# Proactive retrieval with context history
result = await service.retrieve(
    queries=[
        {"role": "user", "content": {"text": "What are their preferences?"}},
        {"role": "user", "content": {"text": "Tell me about work habits"}}
    ],
    where={"user_id": "123"},  # Optional: scope filter
    method="rag"  # or "llm" for deeper reasoning
)

# Returns context-aware results:
{
    "categories": [...],     # Relevant topic areas (auto-prioritized)
    "items": [...],          # Specific memory facts
    "resources": [...],      # Original sources for traceability
    "next_step_query": "..." # Predicted follow-up context
}

Proactive Filtering: Use where to scope continuous monitoring:

  • where={"user_id": "123"} - User-specific context
  • where={"agent_id__in": ["1", "2"]} - Multi-agent coordination
  • Omit where for global context awareness

📚 For complete API documentation, see SERVICE_API.md - includes proactive workflow patterns, pipeline configuration, and real-time update handling.


💡 Proactive Scenarios

Example 1: Always-Learning Assistant

Continuously learns from every interaction without explicit memory commands:

export OPENAI_API_KEY=your_api_key
python examples/example_1_conversation_memory.py

Proactive Behavior:

  • Automatically extracts preferences from casual mentions
  • Builds relationship models from interaction patterns
  • Surfaces relevant context in future conversations
  • Adapts communication style based on learned preferences

Best for: Personal AI assistants, customer support that remembers, social chatbots


Example 2: Self-Improving Agent

Learns from execution logs and proactively suggests optimizations:

export OPENAI_API_KEY=your_api_key
python examples/example_2_skill_extraction.py

Proactive Behavior:

  • Monitors agent actions and outcomes continuously
  • Identifies patterns in successes and failures
  • Auto-generates skill guides from experience
  • Proactively suggests strategies for similar future tasks

Best for: DevOps automation, agent self-improvement, knowledge capture


Example 3: Multimodal Context Builder

Unifies memory across different input types for comprehensive context:

export OPENAI_API_KEY=your_api_key
python examples/example_3_multimodal_memory.py

Proactive Behavior:

  • Cross-references text, images, and documents automatically
  • Builds unified understanding across modalities
  • Surfaces visual context when discussing related topics
  • Anticipates information needs by combining multiple sources

Best for: Documentation systems, learning platforms, research assistants


📊 Performance

MemU achieves 92.09% average accuracy on the Locomo benchmark across all reasoning tasks, demonstrating reliable proactive memory operations.

benchmark

View detailed experimental data: memU-experiment


🧩 Ecosystem

Repository Description Proactive Features
memU Core proactive memory engine 7×24 learning pipeline, auto-categorization
memU-server Backend with continuous sync Real-time memory updates, webhook triggers
memU-ui Visual memory dashboard Live memory evolution monitoring

Quick Links:


🤝 Partners

Ten OpenAgents Milvus xRoute Jazz Buddie Bytebase LazyLLM


🤝 How to Contribute

We welcome contributions from the community! Whether you're fixing bugs, adding features, or improving documentation, your help is appreciated.

Getting Started

To start contributing to MemU, you'll need to set up your development environment:

Prerequisites

  • Python 3.13+
  • uv (Python package manager)
  • Git

Setup Development Environment

# 1. Fork and clone the repository
git clone https://github.com/YOUR_USERNAME/memU.git
cd memU

# 2. Install development dependencies
make install

The make install command will:

  • Create a virtual environment using uv
  • Install all project dependencies
  • Set up pre-commit hooks for code quality checks

Running Quality Checks

Before submitting your contribution, ensure your code passes all quality checks:

make check

The make check command runs:

  • Lock file verification: Ensures pyproject.toml consistency
  • Pre-commit hooks: Lints code with Ruff, formats with Black
  • Type checking: Runs mypy for static type analysis
  • Dependency analysis: Uses deptry to find obsolete dependencies

Contributing Guidelines

For detailed contribution guidelines, code standards, and development practices, please see CONTRIBUTING.md.

Quick tips:

  • Create a new branch for each feature or bug fix
  • Write clear commit messages
  • Add tests for new functionality
  • Update documentation as needed
  • Run make check before pushing

📄 License

Apache License 2.0


🌍 Community


Star us on GitHub to get notified about new releases!

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

memu_py-1.3.0.tar.gz (11.7 MB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

memu_py-1.3.0-cp313-abi3-win_amd64.whl (248.6 kB view details)

Uploaded CPython 3.13+Windows x86-64

memu_py-1.3.0-cp313-abi3-manylinux_2_39_x86_64.whl (384.6 kB view details)

Uploaded CPython 3.13+manylinux: glibc 2.39+ x86-64

memu_py-1.3.0-cp313-abi3-manylinux_2_39_aarch64.whl (376.6 kB view details)

Uploaded CPython 3.13+manylinux: glibc 2.39+ ARM64

memu_py-1.3.0-cp313-abi3-macosx_11_0_arm64.whl (352.7 kB view details)

Uploaded CPython 3.13+macOS 11.0+ ARM64

memu_py-1.3.0-cp313-abi3-macosx_10_12_x86_64.whl (355.3 kB view details)

Uploaded CPython 3.13+macOS 10.12+ x86-64

File details

Details for the file memu_py-1.3.0.tar.gz.

File metadata

  • Download URL: memu_py-1.3.0.tar.gz
  • Upload date:
  • Size: 11.7 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for memu_py-1.3.0.tar.gz
Algorithm Hash digest
SHA256 7e060995e96850ec960554e14c138709dea3d2408767217987b4769f66c82329
MD5 5f706688691d20e19820c0d6ac7a337b
BLAKE2b-256 c151f7e09e701594d2368e4624d287bc63718082aa2da5053f78a7209d29f365

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0.tar.gz:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file memu_py-1.3.0-cp313-abi3-win_amd64.whl.

File metadata

  • Download URL: memu_py-1.3.0-cp313-abi3-win_amd64.whl
  • Upload date:
  • Size: 248.6 kB
  • Tags: CPython 3.13+, Windows x86-64
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for memu_py-1.3.0-cp313-abi3-win_amd64.whl
Algorithm Hash digest
SHA256 e8d4bcdb9dcbc9c386fc6de02cf9e8147ad59bb1e0f9fba0417257ffa46aff7d
MD5 28a8f000803ff23e41810d4216ebdbef
BLAKE2b-256 dd64c35bf062022cf3d5e452da6628fab7226ae56f9b96bb5b67652a55fae51a

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0-cp313-abi3-win_amd64.whl:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file memu_py-1.3.0-cp313-abi3-manylinux_2_39_x86_64.whl.

File metadata

File hashes

Hashes for memu_py-1.3.0-cp313-abi3-manylinux_2_39_x86_64.whl
Algorithm Hash digest
SHA256 9496522e7938b39a2572e74e981dbd516478313c27a3b113171f1ce36fd8926d
MD5 4f2e986bb46457e866cfde4f56865819
BLAKE2b-256 3f757d5599563aa7c7a941867c5e12604054194b7a90a9430304369b92c64c66

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0-cp313-abi3-manylinux_2_39_x86_64.whl:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file memu_py-1.3.0-cp313-abi3-manylinux_2_39_aarch64.whl.

File metadata

File hashes

Hashes for memu_py-1.3.0-cp313-abi3-manylinux_2_39_aarch64.whl
Algorithm Hash digest
SHA256 d4f052140a8e182227c53ed9e5a5433ccbfe5b7182b866f9eb4df7a1dbd49416
MD5 75b908abd32856cf32c3acb08e95905e
BLAKE2b-256 22da0bef35dd2501dddbd3bedac3f7f06f74589d00fa0abf5b64d8dc15f6e25a

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0-cp313-abi3-manylinux_2_39_aarch64.whl:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file memu_py-1.3.0-cp313-abi3-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for memu_py-1.3.0-cp313-abi3-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 56827743ec5cd3eecaee7a4bc8377b62cb8329f820c758d23a50f778dc18e207
MD5 19ac7c67fa76747b0f1295f1bc04b346
BLAKE2b-256 546fcf0b03461b1bcc0f14c7cec61f432a2b9f265af376dc5076b2065ed69e1d

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0-cp313-abi3-macosx_11_0_arm64.whl:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file memu_py-1.3.0-cp313-abi3-macosx_10_12_x86_64.whl.

File metadata

File hashes

Hashes for memu_py-1.3.0-cp313-abi3-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 a95717bf6d12b5ed4140a3ab9c80c85267d246e8c47725191a9f082209fd0b69
MD5 b6fcccf4bdeadde556c92895b3b2a120
BLAKE2b-256 df6825e8d268d9e8bff581e13b9e2136de1e965d379ccf97f61f64730913df8b

See more details on using hashes here.

Provenance

The following attestation bundles were made for memu_py-1.3.0-cp313-abi3-macosx_10_12_x86_64.whl:

Publisher: release-please.yml on NevaMind-AI/memU

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page