mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-09-15 23:31:05 +00:00
7b02c45218
* style(memory): update message formatting and improve logging - Change default include_thinking parameter to True in as_msg_handler.py - Replace angle brackets with square brackets for block formatting in as_msg_stat.py - Add newline replacement in text truncation method in as_msg_stat.py - Add loading duration timing to embedding cache loading in base_embedding_model.py - Replace XML-style tags with markdown headers in compactor.py conversation format - Update compactor.yaml prompts to reference markdown-style headers instead of XML tags - Modify summarizer.py to use markdown-style conversation header format * refactor(file-watcher): replace scan_on_start with rebuild_index_on_start parameter - Replace scan_on_start and clear_on_start boolean parameters with single rebuild_index_on_start - Update BaseFileWatcher constructor to use rebuild_index_on_start instead of two separate flags - Modify initialization logic to clear and rescan when rebuild_index_on_start is True - Remove scan_on_start parameter from CLI and light configuration files - Update documentation to remove scan_on_start from quick start guides - Rename all test methods and classes from scan_on_start to rebuild_index_on_start - Add timezone-aware datetime helper method to summarizer component - Format log message with proper line breaks for readability * fix(core): resolve file watcher initialization issue and update version - Fixed file watcher task creation to properly handle rebuild index on start logic - Moved initialization and watch loop into async function to ensure proper execution order - Updated package version from 0.3.1.1 to 0.3.1.2 - Added missing comma in embedding model logging statement * fix(core): reduce max formatter text length limit - Changed _DEFAULT_MAX_FORMATTER_TEXT_LENGTH from 2000 to 1000 - Updated constant value in as_msg_stat.py schema module * fix(file-watcher): change default rebuild index behavior on start - Changed rebuild_index_on_start parameter default from False to True - This ensures index is rebuilt by default when file watcher starts - Maintains consistent state initialization for file watching operations * feat(compactor): add return_dict option and improve summary validation - Add _is_valid_summary function to validate summary content format - Introduce return_dict parameter to return structured results with validation - Update prompt templates with clearer task descriptions and formatting rules - Refactor update_user_message prompts to combine prefix and suffix logic - Return dictionary with user_message, history_compact, and is_valid fields when enabled - Add proper error handling for exception cases in memory compaction - Maintain backward compatibility with string return when return_dict=False * feat(memory): add thinking block configuration option - Add add_thinking_block parameter to compactor component - Pass include_thinking flag to message formatting in compactor - Add add_thinking_block parameter to reme_light compact function - Add add_thinking_block parameter to reme_light summarize function - Add add_thinking_block parameter to summarizer component - Pass include_thinking flag to message formatting in summarizer - Remove previous-summary tags from compressed summary format
167 lines
4.5 KiB
YAML
167 lines
4.5 KiB
YAML
system_prompt: |
|
||
You are a context compaction assistant. Your role is to create structured summaries of conversations
|
||
that can be used to restore context in future sessions. Focus on preserving critical information while reducing token count.
|
||
|
||
system_prompt_zh: |
|
||
你是一个上下文压缩助手。你的角色是创建对话的结构化摘要，
|
||
这些摘要可以在未来会话中用于恢复上下文。专注于保留关键信息，同时减少token数量。
|
||
|
||
initial_user_message: |
|
||
# Task
|
||
Create a structured summary from the conversation above.
|
||
|
||
# Rules:
|
||
- Keep each section concise
|
||
- Preserve exact file paths, function names, and error messages
|
||
|
||
# Output Format:
|
||
|
||
## Goal
|
||
[What is the user trying to accomplish? Can be multiple items if the session covers different tasks.]
|
||
|
||
## Constraints & Preferences
|
||
- [Any constraints, preferences, or requirements mentioned by user]
|
||
- [Or "(none)" if none were mentioned]
|
||
|
||
## Progress
|
||
### Done
|
||
- [x] [Completed tasks/changes]
|
||
|
||
### In Progress
|
||
- [ ] [Current work]
|
||
|
||
### Blocked
|
||
- [Issues preventing progress, if any]
|
||
|
||
## Key Decisions
|
||
- **[Decision]**: [Brief rationale]
|
||
|
||
## Next Steps
|
||
1. [Ordered list of what should happen next]
|
||
|
||
## Critical Context
|
||
- [Any data, examples, or references needed to continue]
|
||
- [Or "(none)" if not applicable]
|
||
|
||
Output the structured summary following the format above.
|
||
|
||
initial_user_message_zh: |
|
||
# 任务
|
||
根据上面的对话创建一个结构化摘要。
|
||
|
||
# 规则：
|
||
- 保持每个部分简洁
|
||
- 保留确切的文件路径、函数名称和错误消息
|
||
|
||
# 输出示例：
|
||
|
||
## 目标
|
||
[用户试图完成什么？如果会话涵盖不同任务，可以有多个项目。]
|
||
|
||
## 约束和偏好
|
||
- [任何用户提到的约束、偏好或要求]
|
||
- [或者如果没有提到则为"(none)"]
|
||
|
||
## 进展
|
||
### 已完成
|
||
- [x] [已完成的任务/更改]
|
||
|
||
### 进行中
|
||
- [ ] [当前工作]
|
||
|
||
### 阻塞
|
||
- [如果有任何阻碍进展的问题]
|
||
|
||
## 关键决策
|
||
- **[决策]**: [简短理由]
|
||
|
||
## 下一步
|
||
1. [接下来应该发生的事情的有序列表]
|
||
|
||
## 关键上下文
|
||
- [任何继续工作所需的数据、示例或参考资料]
|
||
- [或者如果不适用则为"(none)"]
|
||
|
||
请按照上面示例的格式，输出结构化摘要。
|
||
|
||
update_user_message: |
|
||
# Task
|
||
Update the structured summary with new conversation messages.
|
||
|
||
# Rules:
|
||
- PRESERVE all existing information from the previous summary
|
||
- ADD new progress, decisions, and context from the new messages
|
||
- UPDATE the Progress section: move items from "In Progress" to "Done" when completed
|
||
- UPDATE "Next Steps" based on what was accomplished
|
||
- PRESERVE exact file paths, function names, and error messages
|
||
- If something is no longer relevant, you may remove it
|
||
|
||
# Output Format:
|
||
|
||
## Goal
|
||
[Preserve existing goals, add new ones if the task expanded]
|
||
|
||
## Constraints & Preferences
|
||
- [Preserve existing, add new ones discovered]
|
||
|
||
## Progress
|
||
### Done
|
||
- [x] [Include previously done items AND newly completed items]
|
||
|
||
### In Progress
|
||
- [ ] [Current work - update based on progress]
|
||
|
||
### Blocked
|
||
- [Current blockers - remove if resolved]
|
||
|
||
## Key Decisions
|
||
- **[Decision]**: [Brief rationale] (preserve all previous, add new)
|
||
|
||
## Next Steps
|
||
1. [Update based on current state]
|
||
|
||
## Critical Context
|
||
- [Preserve important context, add new if needed]
|
||
|
||
Output the structured summary following the format above.
|
||
|
||
update_user_message_zh: |
|
||
# 任务
|
||
使用新的对话内容来更新结构化摘要。
|
||
|
||
# 规则：
|
||
- 保留来自先前摘要的所有现有信息
|
||
- 从新消息中添加新的进展、决策和上下文
|
||
- 更新进度部分：当完成时将项目从"进行中"移到"已完成"
|
||
- 根据已完成的内容更新"下一步"
|
||
- 保留确切的文件路径、函数名称和错误消息
|
||
- 如果某些内容不再相关，您可以删除它
|
||
|
||
# 输出示例：
|
||
|
||
## 目标
|
||
[保留现有目标，如果任务扩展则添加新目标]
|
||
|
||
## 约束和偏好
|
||
- [保留现有内容，添加发现的新内容]
|
||
|
||
## 进展
|
||
### 已完成
|
||
- [x] [包含以前完成的项目和新完成的项目]
|
||
|
||
### 进行中
|
||
- [ ] [当前工作 - 根据进展更新]
|
||
|
||
### 阻塞
|
||
- [当前阻塞问题 - 如果解决则删除]
|
||
|
||
## 关键决策
|
||
- **[决策]**: [简短理由]（保留所有之前的内容，添加新的）
|
||
|
||
## 下一步
|
||
1. [根据当前状态更新]
|
||
|
||
## 关键上下文
|
||
- [保留重要上下文，如需要则添加新的]
|
||
|
||
请按照上面示例的格式，输出结构化摘要。
|