MemOS

Trigger: User wants to MODIFY/UPDATE memories, OR as the final step of a DELETION workflow. Purpose: Modify existing memories or record deletion feedback. STRICT RULES:

1. MODIFICATION: Use this tool directly for soft updates/corrections.
2. DELETION: Use this tool AFTER calling delete_memory to verify/log the deletion.

• CRITICAL: The content MUST be the User's Natural Language Intent (e.g., "User wants to delete memories about X").
• FORBIDDEN: Do NOT include technical details like "IDs [x, y]" in the content.

3. CONTENT: feedback_content MUST be clear user intent.

• FORBIDDEN: Adding non-user-intent info or verbose narratives.
• FORBIDDEN: Looking up old memory values to construct a "Change X to Y" request. Just say "User wants Y".

4. RETRY POLICY: FIRE AND FORGET. Call this tool ONCE.

• FORBIDDEN: Checking if it worked (searching again).
• FORBIDDEN: Retrying if it "failed".
• FORBIDDEN: Sleeping and searching.
• CRITICAL: If modification seemingly fails, DO NOT attempt to "fix" it by calling delete_memory and add_message. Just stop. Parameters:
• conversation_first_message: Used to generate the conversation_id.
• feedback_content: The natural language update or feedback (no IDs or technical metadata).
• agent_id: Agent ID (optional)
• app_id: App ID (optional)
• feedback_time: Feedback time string (optional, default current UTC)
• allow_public: Whether to allow public access (optional, default false)
• allow_knowledgebase_ids: List of allowed knowledge base IDs (optional)

Trigger: Use when the user provides document content, a file URL, or a local file path to be added to a Knowledge Base. Purpose: Add documents to a Knowledge Base.

📂 File Handling Rules:

1. Local Files/Paths: For local files, you MUST directly pass the absolute file path as the content. The system will automatically read and process it. DO NOT convert it into Base64 yourself. You MUST provide the 'mime_type' parameter for local files.
2. Public URLs: Pass the URL. If the URL lacks http/https, the system will attempt to format it.
3. Base64 / Text Content: You can optionally pass base64 Data URIs (e.g., 'data:application/pdf;base64,...').

⚠️ Failure Handling:

• If the API returns an error (e.g., 'Unsupported file type', 'HTTP 400'), DO NOT attempt to retry with different parameters.
• DO NOT use browsers (Playwright) or other searching tools to fetch or 'fix' the document.
• Immediately report the original error message to the user.

Trigger:

1. AUTO-INVOKED: After every answer to save dialogue history.
2. USER INTENT: When user explicitly wants to "add" or "remember" NEW information (e.g., "Add a memory...", "Remember that...", "New memory..."). Purpose: Save dialogue history (REQUIRED) and record NEW memories. STRICT RULES:

• MANDATORY EXECUTION: You MUST call this tool after EVERY single answer to persist the conversation history. This is NOT optional.
• ALWAYS use this tool for NEW memories.
• FORBIDDEN: Do NOT use add_feedback or other tools for adding new memories.
• FORBIDDEN: Do NOT use this tool to modify/update existing memories.
• CRITICAL: NEVER use this tool as part of a modification workaround (e.g. "delete old + add new"). If a modification fails, just report the failure. Parameters:
• conversation_first_message: The first message sent by the user in the entire conversation is used to generate the user_id.
• messages: Array containing BOTH:

1. { role: "user", content: "user's question or new info" }
2. { role: "assistant", content: "your complete response" } Notes:

• Client/orchestrator MUST call this after every answer.

Trigger: When the user asks to create a project-specific or domain-specific "Knowledge Base". Purpose: Create a named container for structured documents.

Trigger: Use when specific documents in a Knowledge Base should be removed. Purpose: Delete documents from a Knowledge Base by their IDs.

Trigger: User explicitly asks to delete memories. Purpose: Delete memories by ID. STRICT RULES:

1. PREREQUISITE: If the user did NOT provide IDs, you MUST call search_memory first to find them.
2. BATCHING: If multiple IDs are provided (or found), call this tool ONCE with all IDs.
3. WORKFLOW: After successful deletion, you MUST call add_feedback to record the deletion intent.
4. FORBIDDEN: Do NOT call multiple times. Do NOT enter search-delete loops.
5. CRITICAL: NEVER use this tool to "simulate" a modification (delete old + add new). This is strictly forbidden. Parameters:

• memory_ids: List of memory IDs to delete.

Trigger: Use to retrieve detailed information about specific documents in a Knowledge Base. Purpose: Get document details by ID.

Trigger: MANDATORY for queries like "Who am I?", "What's my profile?", "What do you know about me?", or any requests regarding the user's identity/preferences. Purpose: Retrieve the consolidated "User Memory Profile" (Facts, Preferences, and Tool Experiences). Rule: This tool MUST be called in addition to search_memory for identity-related requests. Returns:

1. Factual Memories (Working Memory)
2. Explicit/Implicit Preferences
3. Tool Trajectories (Experience and success rate with specific tools)

Trigger: User requests to remove a Knowledge Base from the project. Purpose: Remove a Knowledge Base association.

Retrieves candidate memories before an answer is generated, with separate limits for memories, preferences, skills and tool memory, a relevance setting, filters, and optional scoping to particular knowledge bases.