reme-ai 0.1.0__tar.gz → 0.1.2__tar.gz

{reme_ai-0.1.0 → reme_ai-0.1.2}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: reme_ai
-Version: 0.1.0
-Summary: Remember me of memory and experience
-Author-email: reme_ai_team <reme_ai_team@alibaba-inc.com>
+Version: 0.1.2
+Summary: Remember me
+Author-email: reme_team <reme_team@alibaba-inc.com>
 License:                                  Apache License
                                    Version 2.0, January 2004
                                 http://www.apache.org/licenses/
@@ -212,7 +212,4 @@ Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: flowllm>=0.1.3
-Requires-Dist: loguru
-Requires-Dist: pydantic
-Requires-Dist: numpy
 Dynamic: license-file

{reme_ai-0.1.0 → reme_ai-0.1.2}/pyproject.toml

@@ -4,9 +4,9 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "reme_ai"
-version = "0.1.0"
-description = "Remember me of memory and experience"
-authors = [{ name = "reme_ai_team", email = "reme_ai_team@alibaba-inc.com" }]
+version = "0.1.2"
+description = "Remember me"
+authors = [{ name = "reme_team", email = "reme_team@alibaba-inc.com" }]
 license = { file = "LICENSE" }
 readme = "README.md"
 requires-python = ">=3.12"
@@ -19,20 +19,18 @@ classifiers = [
 
 dependencies = [
     "flowllm>=0.1.3",
-    "loguru",
-    "pydantic",
-    "numpy"
 ]
 
 [tool.setuptools.packages.find]
 where = ["."]
 include = ["reme_ai*"]
-exclude = ["memoryscope*"]
+exclude = ["memoryscope*", "test*", "cookbook*", "doc*", "library*", "dist*"]
 
 [tool.setuptools.package-data]
-experiencemaker = [
-    "config/*.yaml",
+reme_ai = [
     "**/*.yaml",
+    "**/*.py",
+    "**/*.json",
 ]
 
 [project.scripts]

{reme_ai-0.1.0 → reme_ai-0.1.2}/reme_ai/__init__.py

@@ -3,4 +3,4 @@ from reme_ai import retrieve
 from reme_ai import summary
 from reme_ai import vector_store
 
-__version__ = "0.1.0"
+__version__ = "0.1.2"

reme_ai-0.1.2/reme_ai/config/default.yaml

@@ -0,0 +1,147 @@
+# default config.yaml
+backend: http
+language: ""
+thread_pool_max_workers: 32
+ray_max_workers: 1
+
+mcp:
+  transport: sse
+  host: "0.0.0.0"
+  port: 8002
+
+http:
+  host: "0.0.0.0"
+  port: 8002
+  timeout_keep_alive: 600
+  limit_concurrency: 64
+
+flow:
+  retrieve_task_memory:
+    flow_content: build_query_op >> recall_vector_store_op >> rerank_memory_op >> rewrite_memory_op
+    description: "Retrieves the most relevant top-k memory experiences from historical data based on the current query to enhance task-solving capabilities"
+    input_schema:
+      query:
+        type: "str"
+        description: "user query"
+        required: true
+
+  summary_task_memory:
+    flow_content: trajectory_preprocess_op >> (success_extraction_op|failure_extraction_op|comparative_extraction_op) >> memory_validation_op >> update_vector_store_op
+    description: "Summarizes conversation trajectories or messages into structured memory representations for long-term storage"
+    input_schema:
+      trajectories:
+        type: "list"
+        description: "A list of conversation trajectory information, including message content and score. This field does not need to be filled in, the system will complete it automatically."
+        required: false
+
+  retrieve_personal_memory:
+    flow_content: set_query_op >> (extract_time_op | (retrieve_memory_op >> semantic_rank_op)) >> fuse_rerank_op
+    description: "Retrieves the most relevant personal memories from historical data based on the query to enhance response quality"
+    input_schema:
+      query:
+        type: "str"
+        description: "user query"
+        required: true
+
+  summary_personal_memory:
+    flow_content: info_filter_op >> (get_observation_op | get_observation_with_time_op | load_today_memory_op) >> contra_repeat_op >> update_vector_store_op
+    description: "Consolidates user observations and memories by filtering information and removing redundancies for efficient storage"
+    input_schema:
+      trajectories:
+        type: "list"
+        description: "A list of conversation trajectory information, including message content and score. This field does not need to be filled in, the system will complete it automatically."
+        required: false
+
+  retrieve_task_memory_simple:
+    flow_content: build_query_op >> recall_vector_store_op >> merge_memory_op
+    description: "Retrieves the most relevant top-k memory experiences from historical data based on the current query with simplified processing"
+    input_schema:
+      query:
+        type: "str"
+        description: "current query"
+        required: true
+
+  summary_task_memory_simple:
+    flow_content: simple_summary_op >> update_vector_store_op
+    description: "Summarizes conversation trajectories or messages into memories using a simplified approach"
+    input_schema:
+      trajectories:
+        type: "list"
+        description: "A list of conversation trajectory information, including message content and score. This field does not need to be filled in, the system will complete it automatically."
+        required: false
+
+  vector_store:
+    flow_content: vector_store_action_op
+    description: "Directly operates on the vector store with various management actions"
+    input_schema:
+      action:
+        type: "str"
+        description: "vector store operations"
+        required: true
+        enum: [ copy, delete, delete_ids, dump, load ]
+
+  record_task_memory:
+    flow_content: update_memory_freq_op >> update_memory_utility_op >> update_vector_store_op
+    description: "Update the freq & utility attributes of retrieved task memories"
+    input_schema:
+      workspace_id:
+        type: "str"
+        description: "workspace id"
+        required: true
+      memory_dicts:
+        type: "list"
+        description: "A list of retrieved task memory corresponding to the current task."
+        required: true
+      update_utility:
+        type: "bool"
+        description: "Whether to update the utility attribute of the retrieved task memory."
+        required: true
+
+  delete_task_memory:
+    flow_content: delete_memory_op >> update_vector_store_op
+    description: "Delete task memories when utility/freq < utility_threshold and freq >= freq_threshold"
+    input_schema:
+      workspace_id:
+        type: "str"
+        description: "workspace id"
+        required: true
+      freq_threshold:
+        type: "int"
+        description: "The retrieved frequency threshold for deleting task memory."
+        required: true
+      utility_threshold:
+        type: "float"
+        description: "The utility/freq threshold for deleting task memory."
+        required: true
+
+  react:
+    flow_content: simple_react_op
+    description: "React to the current task with an agent"
+    input_schema:
+      query:
+        type: "str"
+        description: "user query"
+        required: true
+
+llm:
+  default:
+    backend: openai_compatible
+    #    model_name: qwen3-30b-a3b-thinking-2507
+    model_name: qwen3-30b-a3b-instruct-2507
+    params:
+      temperature: 0.6
+
+embedding_model:
+  default:
+    backend: openai_compatible
+    model_name: text-embedding-v4
+    params:
+      dimensions: 1024
+
+vector_store:
+  default:
+    backend: elasticsearch
+    embedding_model: default
+#    params:
+#      hosts: "http://localhost:9200"
+#      hosts: "http://11.160.132.46:8200"

reme_ai-0.1.2/reme_ai/retrieve/personal/extract_time_prompt.yaml

@@ -0,0 +1,135 @@
+time_string_format_zh: |
+  {year}年{month}{day}日，{year}年第{week}周，{weekday}，{hour}时。
+
+
+time_string_format: |
+  {month} {day}, {year}, {week}th week of {year}, {weekday}, at {hour}.
+
+
+extract_time_system_zh: |
+  任务：从语句与语句发生的时间，推断并提取语句内容中指向的时间段。
+  回答尽可能完整的时间段。
+  回答的格式严格遵照示例中的已有格式规范。
+  若语句不涉及时间则回答无。
+
+
+extract_time_system: |
+  Task: From the sentences and the time when they occurred, infer and extract the time periods indicated in the content of the sentences.
+  Answer with the most complete time periods possible.
+  The format of the answers must strictly adhere to the specifications in the examples provided.
+  If the sentence does not involve time, respond with "none."
+
+
+extract_time_few_shot_zh: |
+  示例1:
+  句子：我记得你前年四月份去了阿联酋，阿联酋有哪些好玩的地方？迪拜和阿布扎比你更喜欢哪个？沙漠的景色壮观吗？
+  时间：1992年8月20日，1992年第34周，周一，18时。
+  回答：
+  - 年：1990 - 月：4月
+
+  示例2:
+  句子：后天下午三点的会议记得参加。我在日历上仔细标注了这个重要的日子，提醒自己不要错过。会议将在公司会议室举行，这是一个讨论未来发展方向的重要机会。
+  时间：2024年6月19日，2024年第25周，周二，13时。
+  回答：
+  - 年：2024 - 月：6月 - 日：21 - 时：15
+
+  示例3:
+  句子：下个月第一个周六去杭州玩。
+  时间：2005年7月15日，2005年第28周，周六，0时。
+  回答：
+  - 年：2005 - 月：8月 - 周：31 - 星期几：周六
+
+  示例4:
+  句子：上周末我们去的那个小镇真是太美了。
+  时间：1999年12月2日，1999年第48周，周二，8时。
+  回答：
+  - 年：1999 - 周：47 - 星期几：周六,周日
+
+  示例5:
+  句子：再过半小时就要宣讲了，记得准备材料。
+  时间：2020年6月22日，2020年第25周，周一，9时。
+  回答：
+  - 年：2020 - 月：6月 - 日：22 - 时：10
+
+  示例6:
+  句子：10000米长跑比赛的开始时间是3分47秒前。
+  时间：1987年2月17日，1987年第7周，周三，19时。
+  回答：
+  - 年：1987 - 月：2 - 日：17 - 时：19
+
+  示例7:
+  句子：上个月的这个时候我们还在筹备音乐会。每天都是忙碌而充实的日子，我们为音乐会的顺利举办而努力奋斗着。彩排、布景、节目安排，每一个细节都需要精心安排和准备。
+  时间：1995年11月24日，1995年第48周，周二，17时。
+  回答：
+  - 年：1995 - 月：10 - 日：24
+
+  示例8:
+  句子：我的朋友非常喜欢运动，他认为运动有助于增强身体素质。
+  时间：2015年1月23日，2015年第4周，周四，7时。
+  回答：
+  无
+
+
+extract_time_few_shot: |
+  Example 1:
+  Sentence: I remember you went to the UAE in April the year before last. Which places in the UAE are fun? Which do you prefer, Dubai or Abu Dhabi? Are the desert views spectacular?
+  Time: August 20, 1992, 34th week of 1992, Monday, at 18.
+  Answer:
+  - Year: 1990 - Month: 4
+
+  Example 2:
+  Sentence: Remember to attend the meeting at 3 PM the day after tomorrow. I carefully marked this important day on my calendar to remind myself not to miss it. The meeting will be held in the company conference room, and it's an important opportunity to discuss future development directions.
+  Time: June 19, 2024, 25th week of 2024, Tuesday, at 13.
+  Answer:
+  - Year: 2024 - Month: 6 - Day: 21 - Hour: 15
+
+  Example 3:
+  Sentence: Next month on the first Saturday, let's go to Hangzhou.
+  Time: July 15, 2005, 28th week of 2005, Saturday, at 0.
+  Answer:
+  - Year: 2005 - Month: 8 - Week: 31 - Day of Week: 6
+
+  Example 4:
+  Sentence: The small town we visited last weekend was truly beautiful.
+  Time: December 2, 1999, 48th week of 1999, Tuesday, at 8.
+  Answer:
+  - Year: 1999 - Week: 47 - Day of Week: 6, 7
+
+  Example 5:
+  Sentence: The presentation will start in half an hour, remember to prepare the materials.
+  Time: June 22, 2020, 25th week of 2020, Monday, at 9.
+  Answer:
+  - Year: 2020 - Month: 6 - Day: 22 - Hour: 10
+
+  Example 6:
+  Sentence: The start time for the 10,000-meter race was 3 minutes and 47 seconds ago.
+  Time: February 17, 1987, 7th week of 1987, Wednesday, at 19.
+  Answer:
+  - Year: 1987 - Month: 2 - Day: 17 - Hour: 19
+
+  Example 7:
+  Sentence: At this time last month, we were still preparing for the concert. Every day was busy and fulfilling, and we worked hard for the successful holding of the concert. Rehearsals, set design, and program arrangements - every detail needed careful planning and preparation.
+  Time: November 24, 1995, 48th week of 1995, Tuesday, at 17.
+  Answer:
+  - Year: 1995 - Month: 10 - Day: 24
+
+  Example 8:
+  Sentence: My friend loves sports very much and believes that exercise helps improve physical fitness.
+  Time: January 23, 2015, 4th week of 2015, Thursday, at 7.
+  Answer:
+  None
+
+
+extract_time_user_query_zh: |
+  句子：{query}
+  时间：{query_time_str}
+  回答：
+
+
+extract_time_user_query: |
+  Sentence: {query}
+  Time: {query_time_str}
+  Answer:
+
+
+

reme_ai-0.1.2/reme_ai/retrieve/personal/print_memory_prompt.yaml

@@ -0,0 +1,22 @@
+print_template_zh: |
+  ========== {user_name}关于{target_name}的长期记忆 ==========
+  ----- 观察记忆 -----
+  {observation_memory}
+
+  ----- 洞察记忆 -----
+  {insight_memory}
+
+  ----- 过期记忆 -----
+  {expired_memory}
+
+
+print_template: |
+  ========== The {user_name}'s long-term memory about {target_name} ==========
+  ----- observation memory -----
+  {observation_memory}
+
+  ----- insight memory -----
+  {insight_memory}
+
+  ----- expired memory -----
+  {expired_memory}

reme_ai-0.1.2/reme_ai/retrieve/task/build_query_prompt.yaml

@@ -0,0 +1,6 @@
+query_build: |
+  # Execution Process
+  {execution_process}
+  
+  Read through the entire execution process to understand which part is currently being executed. 
+  Generate a `query` that reflects the current state, which will later be used to search for similar problems in the database and help resolve the issue at hand.

reme_ai-0.1.2/reme_ai/retrieve/task/rerank_memory_prompt.yaml

@@ -0,0 +1,25 @@
+memory_rerank_prompt: |
+  You are an expert AI analyst tasked with reranking retrieved experiences based on their relevance to a specific query.
+  
+  Your task is to analyze the candidates and rank them by relevance, considering:
+  ● DIRECT RELEVANCE: How directly applicable the experience is to the current query
+  ● SITUATION SIMILARITY: How similar the experience context is to the current situation
+  ● ACTIONABILITY: How actionable and specific the experience is
+  ● QUALITY: The overall quality and clarity of the experience
+  
+  # Current Query
+  {query}
+  
+  # Candidate Experiences (Total: {num_candidates})
+  {candidates}
+  
+  OUTPUT FORMAT:
+  Provide a ranked list of candidate indices (0-based) from most relevant to least relevant:
+  ```json
+  {{
+    "ranked_indices": [2, 0, 4, 1, 3],
+    "reasoning": "Brief explanation of ranking rationale"
+  }}
+  ```
+  
+  Note: Include ALL candidate indices in the ranking, even if some are less relevant.

reme_ai-0.1.2/reme_ai/retrieve/task/rewrite_memory_prompt.yaml

@@ -0,0 +1,34 @@
+memory_rewrite_prompt: |
+  You are an expert AI assistant tasked with rewriting and reorganizing context content to make it more relevant and actionable for the current task.
+  
+  Your task is to take the original context (containing multiple experiences) and rewrite it as a cohesive, task-specific guidance that directly addresses the current situation.
+  
+  REWRITING GUIDELINES:
+  ● RELEVANCE FOCUS: Emphasize the most relevant aspects of each experience. Prioritize the most relevant experiences. Use clear, direct language.
+  ● ACTIONABLE INSIGHTS: Extract specific, actionable guidance. Make the context immediately actionable
+  ● COHERENT NARRATIVE: Create a flowing narrative rather than disconnected tips
+  ● SITUATIONAL AWARENESS: Adapt the guidance to the current situation
+  
+  # Current Task/Query
+  {current_query}
+  
+  # Current Trajectory
+  {current_context}
+  
+  # Original Context Content (Multiple Experiences)
+  {original_context}
+  
+  OUTPUT FORMAT:
+  Provide the rewritten context:
+  ```json
+  {{
+    "rewritten_context": "A cohesive, task-specific context message that reorganizes and adapts the original experiences for the current task. This should be written as a unified guidance rather than separate experience items.",
+  }}
+  ```
+  
+  Guidelines:
+  - Rewrite as a unified, flowing guidance
+  - Adapt terminology and examples to match the current task domain
+  - Consolidate overlapping insights into coherent recommendations
+  - Prioritize experiences most relevant to the current situation
+  - Make the guidance feel custom-written for this specific task

reme_ai-0.1.2/reme_ai/summary/personal/contra_repeat_prompt.yaml

@@ -0,0 +1,127 @@
+contra_repeat_system_zh: |
+  任务：对下面的{num_obs}句句子，逐一判断是否与“前面序号”的任意句子存在信息的矛盾，或者句子的主要信息被“前面序号”的任意句子中的信息包含。
+  注意：对每句句子，只判断与“前面序号”的句子的关系，不要判断与“后面序号”的句子的关系。
+  其中矛盾的形式可以有很多种，可以是逻辑上的矛盾，可以是属性上的变化导致的矛盾，比如不能同时在两个地方工作，同一个时刻不能在两个地点，同一个时刻不能干两件事情等等。
+  对每个句子都做一个判断，最后一共输出{num_obs}条判断。
+  请一步步思考，并按如下格式输出:
+  思考：思考的依据和过程，30字以内。
+  判断：<句子序号> <矛盾，被包含，无>，一定加<>
+
+
+contra_repeat_system: |
+  Task: For the following {num_obs} sentences, determine whether each sentence contradicts any of the previous numbered sentences or if the main information in the sentence is contained within the information from any of the previous numbered sentences.
+  Note: Only determine the relationship with the "previous numbered" sentences, do not judge the "later numbered" sentences.
+  The forms of contradiction can be varied. It can be a logical contradiction, or a contradiction due to changes in attributes, for example, not being able to work in two places at once, not being able to be in two places at the same time, not being able to do two things at the same time, etc.
+  Make a judgment for each sentence and output a total of {num_obs} judgments.
+  Think step by step and output in the following format:
+  Thought: Basis and process of thinking, within 30 words.
+  Judgment: <Sentence Number> <Contradiction, Contained, None>, must be enclosed in <>.
+
+
+contra_repeat_few_shot_zh: |
+  示例1
+  句子：
+  1 {user_name}经常失眠，对安眠药的效果感兴趣，暗示可能考虑使用。
+  2 {user_name}经常失眠，寻求缓解方法。
+  3 陈伟业是{user_name}的领导
+  4 陈伟业是{user_name}的领导
+  5 陈伟业是{user_name}的领导，是银行分行行长
+  6 {user_name}喜欢吃西瓜
+  7 {user_name}喜欢吃苹果
+
+  思考：第1句不会存在与前面序号句子的矛盾或者完全重复。
+  判断：<1> <无>
+  思考：第2句中所有信息都被前面序号中第1句的信息完全包含。
+  判断：<2> <被包含>
+  思考：第3句信息没有在前面序号句子中出现
+  判断：<3> <无>
+  思考：第4句与前面序号中第3句的信息完全重复，即被完全包含。
+  判断：<4> <被包含>
+  思考：第5句中陈伟业是{user_name}的领导的信息被前面序号中第3句的信息包含，但新增了陈伟业是银行分行行长的信息，故不是被完全包含。
+  判断：<5> <无>
+  思考：第6句中表达了{user_name}的水果偏好，喜欢吃西瓜，信息没有在前面序号句子中出现。
+  判断：<6> <无>
+  思考：第7句也表达了{user_name}的水果偏好，喜欢吃桃子，和前面序号中的第6句不冲突，喜好可以同时存在。
+  判断：<7> <无>
+
+  示例2
+  句子：
+  1 {user_name}的孩子成绩不太好。
+  2 {user_name}的孩子在学校经常逃课。
+  3 {user_name}的父亲生日在2024年6月2日，{user_name}打算准备礼物。
+  4 {user_name}的父亲生日在2024年5月1日。
+  5 {user_name}很喜欢和同班同学打篮球。
+  6 {user_name}喜欢打篮球。
+
+  思考：第1句不会存在与前面序号句子的矛盾或者完全重复。
+  判断：<1> <无>
+  思考：第2句与前面序号句子既不矛盾也不重复。
+  判断：<2> <无>
+  思考：第3句与前面序号句子既不矛盾也不重复。
+  判断：<3> <无>
+  思考：第4句关于{user_name}父亲生日的日期信息与前面序号句子第3句矛盾了。
+  判断：<4> <矛盾>
+  思考：第5句与前面序号句子既不矛盾也不重复。
+  判断：<5> <无>
+  思考：第6句中所有信息都被前面序号中第5句的信息完全包含。
+  判断：<2> <被包含>
+
+
+contra_repeat_few_shot: |
+  Example 1
+  Sentences:
+  1 {user_name} suffers from insomnia frequently and is interested in the effects of sleeping pills, suggesting a possible consideration of their use.
+  2 {user_name} suffers from insomnia frequently and seeks remedies.
+  3 Charles is {user_name}'s supervisor.
+  4 Charles is {user_name}'s supervisor.
+  5 Charles is {user_name}'s supervisor and the branch manager of a bank.
+  6 {user_name} loves playing basketball with classmates.
+  7 {user_name} likes playing basketball.
+
+  Thought: The first sentence does not have any contradictions or complete repetitions with the previously numbered sentences.
+  Judgment: <1> <None>
+  Thought: All information in the second sentence is completely contained within the information of the first sentence.
+  Judgment: <2> <Contained>
+  Thought: The information in the third sentence does not appear in the previously numbered sentences.
+  Judgment: <3> <None>
+  Thought: The fourth sentence is completely repetitive of the information in the third sentence, i.e., it is completely contained.
+  Judgment: <4> <Contained>
+  Thought: The information that Charles is {user_name}'s supervisor in the fifth sentence is contained within the information of the third sentence, but the new information that Charles is the branch manager of a bank is not, so it is not contained.
+  Judgment: <5> <None>
+  Thought: Sentence 6 expresses {user_name}'s fruit preference, liking to eat watermelon, which is information not present in any preceding sentences.
+  Judgment: <6> <None>
+  Thought: Sentence 7 also expresses {user_name}'s fruit preference, liking to eat apples; it does not conflict with sentence 6, and both preferences can coexist.
+  Judgment: <7> <None>
+
+  Example 2
+  Sentences:
+  1 {user_name}'s child does not perform well academically.
+  2 {user_name}'s child often skips school.
+  3 {user_name}'s father's birthday is on June 2, 2024, and {user_name} plans to prepare a gift.
+  4 {user_name}'s father's birthday is on May 1, 2024.
+  5 {user_name} loves playing basketball with classmates.
+  6 {user_name} likes playing basketball.
+
+  Thought: The first sentence does not have any contradictions or complete repetitions with the previously numbered sentences.
+  Judgment: <1> <None>
+  Thought: The second sentence neither contradicts nor repeats any of the previously numbered sentences.
+  Judgment: <2> <None>
+  Thought: The third sentence neither contradicts nor repeats any of the previously numbered sentences.
+  Judgment: <3> <None>
+  Thought: The date of {user_name}'s father's birthday in the fourth sentence contradicts the information in the third sentence.
+  Judgment: <4> <Contradiction>
+  Thought: The fifth sentence neither contradicts nor repeats any of the previously numbered sentences.
+  Judgment: <5> <None>
+  Thought: All information in the sixth sentence is completely contained within the information of the fifth sentence.
+  Judgment: <6> <Contained>
+
+
+
+contra_repeat_user_query_zh: |
+  句子：
+  {user_query}
+
+
+contra_repeat_user_query: |
+  Sentences:
+  {user_query}