​

update_memory

​

Use Cases

• Correct inaccurate information
• Add additional context to existing memories
• Update preferences that have changed
• Refine memory content for clarity

​

Parameters

​

Response

​

Example Request

{
  "memory_id": "550e8400-e29b-41d4-a716-446655440000",
  "content": "User prefers dark mode UI and always uses GPT-4 Turbo for code generation"
}

​

Example Response

{
  "success": true,
  "memory": {
    "memory_id": "550e8400-e29b-41d4-a716-446655440000",
    "content": "User prefers dark mode UI and always uses GPT-4 Turbo for code generation",
    "created_at": "2025-02-02T12:00:00Z",
    "updated_at": "2025-02-02T14:30:00Z",
    "agent_id": "agent_123",
    "agent_name": "Code Assistant",
    "api_key_id": "key_456"
  },
  "message": "Memory updated successfully"
}

​

Behavior

• Content is trimmed of leading/trailing whitespace before updating
• The updated_at timestamp is automatically set to the current time
• The embedding in ChromaDB is updated in the background
• Only memories created by the same API key can be updated

​

Error Handling

​

Ownership

• Security: API keys can only modify their own memories
• Accountability: You can track which API key created each memory
• Isolation: Different API keys don’t interfere with each other’s memories

​

Best Practices

1. Verify ownership first: Use get_memories to find memories you can update
2. Preserve context: When updating, include the original information plus new details
3. Update promptly: Update memories when information changes
4. Don’t duplicate: Update existing memories rather than creating duplicates