langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1590] [MERGED] Add mem0ai plugin: Local-only Mem0 AI memory management #1707

New Issue
Closed
opened 2026-02-22 18:05:42 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:05:42 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1590
Author: @beersoccer
Created: 11/23/2025
Status: ✅ Merged
Merged: 11/25/2025
Merged by: @crazywoola

Base: main ← Head: main

📝 Commits (10+)

  • 43ae89d Create README.md for Mem0 Dify Plugin v0.1.3
  • eea4e82 Add Mem0 plugin package
  • 74f154c Add placeholder text to README.md
  • 3ad86f0 Upload mem0ai plugin package
  • f28be18 Delete beersoccer/tools directory
  • 227dbea Delete beersoccer/mem0ai/README.md
  • 99d227d Delete beersoccer/mem0ai/mem0-0.1.3.difypkg
  • e40ee70 Add README.md file with initial content
  • 53bbb40 Upload mem0ai plugin package
  • 6e5aee5 Delete beersoccer/mem0ai/README.md

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ beersoccer/mem0ai/mem0ai-0.1.3.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission

  • Version update for existing plugin

3. Description

This plugin integrates Mem0 AI's intelligent memory layer into Dify, providing comprehensive memory management capabilities for AI applications. The plugin operates exclusively in local mode, allowing users to configure and manage their own LLM, embedding models, vector databases, graph databases, and rerankers.

Key Features:

  • 8 Complete Memory Management Tools:

    • Add Memory - Intelligently add, update, or delete memories based on user interactions
    • Search Memory - Search with advanced filters (AND/OR logic) and top_k limiting
    • Get All Memories - List memories with pagination
    • Get Memory - Fetch specific memory details
    • Update Memory - Modify existing memories
    • Delete Memory - Remove individual memories
    • Delete All Memories - Batch delete with filters
    • Get Memory History - View change history

  • Flexible Operation Modes:

    • Async Mode (default): Recommended for production, supports high concurrency with non-blocking write operations
    • Sync Mode: Recommended for testing, all operations block until completion for immediate result visibility

  • Local-Only Architecture:

    • All data stored in user's own infrastructure (vector database, graph database)
    • No data sent to external servers
    • Complete user control over data storage and processing

  • Production-Ready Features:

    • Comprehensive timeout protection and service degradation
    • Robust error handling ensuring workflow continuity
    • Database connection pool optimization for high concurrency
    • Unified logging configuration for better debugging

Configuration:

Users configure the plugin by:

  1. Choosing operation mode (async/sync)
  2. Providing JSON configurations for:
    • LLM provider (required)
    • Embedding model (required)
    • Vector database (required, e.g., pgvector)
    • Graph database (optional, e.g., Neo4j)
    • Reranker (optional)

For detailed configuration options, users are directed to the Mem0 Official Configuration Documentation.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines

  • I have read and comply with the Plugin Developer Agreement

  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version

  • I confirm my plugin has been thoroughly tested for completeness and functionality

  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions

  • Detailed usage instructions

  • All required APIs and credentials are clearly listed

  • Connection requirements and configuration details

  • Link to the repository for the plugin source code

Documentation Details:

  • README.md: Includes comprehensive installation guide, configuration examples, usage examples, and links to Mem0 official documentation
  • INSTALL.md: Detailed installation and configuration guide in Chinese
  • GUIDE.md: Configuration guide with detailed examples
  • PRIVACY.md: Complete privacy policy explaining local mode operation
  • CHANGELOG.md: Detailed version history and changes

All configuration examples follow the format specified in Mem0 official documentation, and users are directed to the official docs for advanced configuration options.

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

No user personal data is collected by this plugin.

This plugin operates exclusively in local mode, which means:

  • All data is stored in the user's own infrastructure - Users configure and manage their own vector database and graph database
  • No data is sent to external servers - All processing happens locally using user-configured services (LLM, embedding models, databases)
  • Complete user control - Users have full control over where and how their data is stored

The plugin only processes:

  • Conversation history (chat messages) - stored in user's own vector database
  • User IDs, Agent IDs, Run IDs - used for data partitioning and scoping within user's own database
  • Message metadata (timestamps, roles) - stored in user's own database

No personal identification information (PII) is required or collected beyond user-provided identifiers (user_id, agent_id, run_id).

All API keys and credentials are stored locally in the user's Dify instance configuration and are not shared with any third parties. The plugin only communicates with services configured by the user (their LLM, embedding, and database services).

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

Privacy Policy Location: PRIVACY.md is included in the plugin package and clearly explains:

  • Local mode operation and data storage
  • Information processed by the plugin
  • User's complete control over data
  • No third-party data sharing
  • User's responsibility for data security and compliance

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1590 **Author:** [@beersoccer](https://github.com/beersoccer) **Created:** 11/23/2025 **Status:** ✅ Merged **Merged:** 11/25/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (10+) - [`43ae89d`](https://github.com/langgenius/dify-plugins/commit/43ae89d918be6a91a9870e1eba4d8de95e20330c) Create README.md for Mem0 Dify Plugin v0.1.3 - [`eea4e82`](https://github.com/langgenius/dify-plugins/commit/eea4e8232b47f865de4b23149620c992f0cdb7e5) Add Mem0 plugin package - [`74f154c`](https://github.com/langgenius/dify-plugins/commit/74f154c2c9d9d2a96c7da79392f39f3d337ee9cd) Add placeholder text to README.md - [`3ad86f0`](https://github.com/langgenius/dify-plugins/commit/3ad86f0e4ca8bd8367a159d5cc993adbd4a764fb) Upload mem0ai plugin package - [`f28be18`](https://github.com/langgenius/dify-plugins/commit/f28be1875689168f9fb2bc5eb865790219db7e94) Delete beersoccer/tools directory - [`227dbea`](https://github.com/langgenius/dify-plugins/commit/227dbea5c1454196eead3ec63fd40f0178f1c11f) Delete beersoccer/mem0ai/README.md - [`99d227d`](https://github.com/langgenius/dify-plugins/commit/99d227d0dee982eaa259063c9a26fb73f474caff) Delete beersoccer/mem0ai/mem0-0.1.3.difypkg - [`e40ee70`](https://github.com/langgenius/dify-plugins/commit/e40ee70a44036db44d7bfdc4ee1b0df4d8ab5944) Add README.md file with initial content - [`53bbb40`](https://github.com/langgenius/dify-plugins/commit/53bbb404e626540c4c473eb3e9c61013bd1e00f9) Upload mem0ai plugin package - [`6e5aee5`](https://github.com/langgenius/dify-plugins/commit/6e5aee57f922dbb9570fafada3ae85c38a7efe73) Delete beersoccer/mem0ai/README.md ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `beersoccer/mem0ai/mem0ai-0.1.3.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: beersoccer - **Plugin Name**: mem0ai - **Repository URL**: https://github.com/beersoccer/mem0_dify_plugin ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> This plugin integrates [Mem0 AI](https://mem0.ai)'s intelligent memory layer into Dify, providing comprehensive memory management capabilities for AI applications. The plugin operates exclusively in **local mode**, allowing users to configure and manage their own LLM, embedding models, vector databases, graph databases, and rerankers. ### Key Features: - **8 Complete Memory Management Tools**: - Add Memory - Intelligently add, update, or delete memories based on user interactions - Search Memory - Search with advanced filters (AND/OR logic) and top_k limiting - Get All Memories - List memories with pagination - Get Memory - Fetch specific memory details - Update Memory - Modify existing memories - Delete Memory - Remove individual memories - Delete All Memories - Batch delete with filters - Get Memory History - View change history - **Flexible Operation Modes**: - **Async Mode** (default): Recommended for production, supports high concurrency with non-blocking write operations - **Sync Mode**: Recommended for testing, all operations block until completion for immediate result visibility - **Local-Only Architecture**: - All data stored in user's own infrastructure (vector database, graph database) - No data sent to external servers - Complete user control over data storage and processing - **Production-Ready Features**: - Comprehensive timeout protection and service degradation - Robust error handling ensuring workflow continuity - Database connection pool optimization for high concurrency - Unified logging configuration for better debugging ### Configuration: Users configure the plugin by: 1. Choosing operation mode (async/sync) 2. Providing JSON configurations for: - LLM provider (required) - Embedding model (required) - Vector database (required, e.g., pgvector) - Graph database (optional, e.g., Neo4j) - Reranker (optional) For detailed configuration options, users are directed to the [Mem0 Official Configuration Documentation](https://docs.mem0.ai/open-source/configuration). ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code **Documentation Details:** - **README.md**: Includes comprehensive installation guide, configuration examples, usage examples, and links to Mem0 official documentation - **INSTALL.md**: Detailed installation and configuration guide in Chinese - **GUIDE.md**: Configuration guide with detailed examples - **PRIVACY.md**: Complete privacy policy explaining local mode operation - **CHANGELOG.md**: Detailed version history and changes All configuration examples follow the format specified in Mem0 official documentation, and users are directed to the official docs for advanced configuration options. ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection **No user personal data is collected by this plugin.** This plugin operates exclusively in **local mode**, which means: - **All data is stored in the user's own infrastructure** - Users configure and manage their own vector database and graph database - **No data is sent to external servers** - All processing happens locally using user-configured services (LLM, embedding models, databases) - **Complete user control** - Users have full control over where and how their data is stored The plugin only processes: - Conversation history (chat messages) - stored in user's own vector database - User IDs, Agent IDs, Run IDs - used for data partitioning and scoping within user's own database - Message metadata (timestamps, roles) - stored in user's own database **No personal identification information (PII) is required or collected beyond user-provided identifiers (user_id, agent_id, run_id).** All API keys and credentials are stored locally in the user's Dify instance configuration and are not shared with any third parties. The plugin only communicates with services configured by the user (their LLM, embedding, and database services). ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines **Privacy Policy Location**: `PRIVACY.md` is included in the plugin package and clearly explains: - Local mode operation and data storage - Information processed by the plugin - User's complete control over data - No third-party data sharing - User's responsibility for data security and compliance --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:05:42 -05:00
yindo closed this issue 2026-02-22 18:05:42 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1707
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?