Memory with Dream
Let the service be accessible instead of re-recognizing the user every time.
Use short-term context to continue the current task, use avatar memory to accumulate stable information, and bring useful context back to subsequent interactions through organization and recall.
Your product, why do you need it?
Your product, why do you need it?
Long-term services cannot require users to repeat the background every time, nor can they infinitely spell all historical conversations into prompt words. Current tasks and long-term preferences require different ways of storing and using them.
How to access your business?
How to access your business?
The following is an illustration of the implementation path. The business interface will not be called or commands will be executed on the official website.
- 01
Distinguish between temporary and long-term
Separate the current task context from long-term facts and preferences, and first clarify the information that the business really needs to continue.
Check the outputContextual strategies and memory retention scope - 02
View the finishing process
Check the memory record and Dream operation entry in the management interface to check whether the sorting task is executed according to the actual configuration.
Check the outputViewable records and organization status - 03
Verify in new session
Initiate follow-up questions on the same avatar, check the recall traces and answers, and then test the range boundaries of different avatars.
Check the outputRecall results and scope testing for specified issues
Use with other base capabilities
Use with other base capabilities
These capabilities belong to the same basic platform and can be combined according to business needs.