You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/overview/quick_start/overview.md
+43-57Lines changed: 43 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ When building applications with large models, a common problem is: **How can AI
29
29
MemOS provides two core APIs to help you achieve this:
30
30
31
31
-`addMessage` — Submit raw conversations to us, we automatically process and store them as memory
32
-
-`searchMemory` — Recall relevant memories and optional suggested instructions in subsequent conversations, making AI responses more aligned with user needs
32
+
-`searchMemory` — Recall factual memories and preference memories in subsequent conversations, so that the AI's responses are more aligned with the user's needs
{"role": "user", "content": "I want to travel during summer vacation, can you recommend something?"},
59
-
{"role": "assistant", "content": "Sure! Are you traveling alone or with family/friends?"},
60
-
{"role": "user", "content": "Of course I’m bringing my kid, our family always travels together."},
61
-
{"role": "assistant", "content": "Got it, so you’re traveling with your children as a family, right?"},
62
-
{"role": "user", "content": "Yes, with both kids and elderly, we usually travel as a whole family."},
63
-
{"role": "assistant", "content": "Understood, I’ll recommend destinations suitable for family trips."}
59
+
{"role": "user", "content": "I’ve planned to travel to Guangzhou this summer. What chain hotels are available for accommodation?"},
60
+
{"role": "assistant", "content": "You can consider options like 7 Days Inn, All Seasons, Hilton, etc."},
61
+
{"role": "user", "content": "I’ll choose 7 Days Inn."},
62
+
{"role": "assistant", "content": "Alright, feel free to ask me if you have any other questions."}
64
63
],
65
64
"user_id": "memos_user_123",
66
65
"conversation_id": "0610"
@@ -83,17 +82,9 @@ print(res.json())
83
82
::note
84
83
**Conversation B: occurred on 2025-09-28**<br>
85
84
86
-
In a new conversation, when the user asks AI to recommend a National Day trip plan, MemOS automatically recalls relevant memories for AI reference, enabling more personalized recommendations.
85
+
When the user asks in a new session for National Day travel and hotel recommendations, MemOS automatically recalls factual (where they’ve been) and preference memories (hotel choices) to help the AI give more personalized suggestions.
87
86
::
88
87
89
-
> MemOS supports returning **`related memories (matches)`**, **`stitched instructions (instruction)` (coming soon)**, and **`full instructions (full_instruction)` (coming soon)** simultaneously. In practice, you only need to choose one based on your business needs.
90
-
91
-
> -**Need full control** → use **matches**, only returns memory items, developers manually stitch them into instructions;
92
-
> -**Want to save stitching work, but still need to add business rules** → use **instruction**, system has combined memories and user query into semi-finished instructions, developers can further refine them;
93
-
> -**Pursue one-click direct use** → use **full_instruction**, system has generated complete terminal instructions ready to be sent to the model.
94
-
95
-
> **Why this design**: Most memory systems stop at “recalling facts”, but facts ≠ executable Prompts. MemOS’s unique instruction completion chain saves you from complex stitching and fine-tuning, directly converting memories into model-readable and executable prompts.
#The user always travels with their whole family (including kids and elderly).
153
-
#Directly answer “Where to go for National Day travel?” and prioritize family-friendly destinations.
154
-
#If information is insufficient, first ask clarification questions before giving suggestions.
114
+
115
+
#Example output (simplified for easier understanding, for reference only)
116
+
117
+
#Preference Memory
118
+
#preference_detail_list [
119
+
#{
120
+
# "preference_type": "implicit_preference",
121
+
# "preference": "Preference for budget-friendly accommodations.",
122
+
# "reasoning": "The user's choice of 7 Days Inn over other options like Hilton suggests a potential preference for more budget-friendly accommodations. 7 Days Inn is known for being an economical option compared to Hilton, which is a higher-end hotel chain. This choice indicates that the user might prioritize cost-effectiveness in their accommodation decisions.",
123
+
# "conversation_id": "0610"
124
+
# }
125
+
# ]
126
+
127
+
#Fact Memory
128
+
#memory_detail_list [
129
+
# {
130
+
# "memory_key": "Summer travel plans to Guangzhou",
131
+
# "memory_value": "The user has planned to travel to Guangzhou during the summer of 2024 and has chosen to stay at 7 Days Inn for accommodation.",
132
+
# "conversation_id": "0610",
133
+
# "tags": [
134
+
# "travel",
135
+
# "Guangzhou",
136
+
# "accommodation",
137
+
# "hotel choice"
138
+
# ]
139
+
# }
140
+
# ]
155
141
```
156
142
157
143
## 2. Option Two: Open-source Framework
@@ -170,13 +156,13 @@ Here we will explain in detail **how a message entering the system is processed
170
156
171
157
::note
172
158
**Deep Understanding**<br>
173
-
MemOS’s memory mechanism can be understood as a complete “workflow”:
174
-
You submit raw messages → Processed into memory → Scheduling mechanism arranges invocation and storage based on task and context, and dynamically adjusts memory forms → Relevant memories are recalled when needed and injected as context or instructions → Lifecycle management ensures evolution and updates.
159
+
MemOS’s memory mechanism works like a complete “workflow”:
160
+
You send a message → the system processes it into memory → the scheduler decides when to store or use it based on context and tasks, and can adjust its form → related memories are recalled when needed → meanwhile, lifecycle management keeps them evolving and updated.
0 commit comments