mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-10-05 02:41:43 +00:00
8b1698451e
* fix(logger): handle file logging configuration errors gracefully * fix(embedding): handle embedding dimension mismatches and improve caching * fix(file-watcher): clear file store on changes to prevent stale data * refactor(logger): update logger implementation and fix message translation * refactor(logger): update logger configuration and add documentation
160 lines
4.9 KiB
YAML
160 lines
4.9 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: |
|
||
The messages above are a conversation to summarize. Create a structured context checkpoint summary
|
||
that another LLM will use to continue the work.
|
||
|
||
Use this EXACT 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]
|
||
|
||
Keep each section concise. Preserve exact file paths, function names, and error messages.
|
||
|
||
initial_user_message_zh: |
|
||
上述消息是一场需要总结的对话。创建一个结构化的上下文检查点摘要，
|
||
以便另一个LLM可以用来继续工作。
|
||
|
||
使用此确切格式：
|
||
|
||
## 目标
|
||
[用户试图完成什么？如果会话涵盖不同任务，可以有多个项目。]
|
||
|
||
## 约束和偏好
|
||
- [任何用户提到的约束、偏好或要求]
|
||
- [或者如果没有提到则为"(none)"]
|
||
|
||
## 进展
|
||
### 已完成
|
||
- [x] [已完成的任务/更改]
|
||
|
||
### 进行中
|
||
- [ ] [当前工作]
|
||
|
||
### 阻塞
|
||
- [如果有任何阻碍进展的问题]
|
||
|
||
## 关键决策
|
||
- **[决策]**: [简短理由]
|
||
|
||
## 下一步
|
||
1. [接下来应该发生的事情的有序列表]
|
||
|
||
## 关键上下文
|
||
- [任何继续工作所需的数据、示例或参考资料]
|
||
- [或者如果不适用则为"(none)"]
|
||
|
||
保持每个部分简洁。保留确切的文件路径、函数名称和错误消息。
|
||
|
||
update_user_message_prefix: |
|
||
The messages above are NEW conversation messages to incorporate into the existing summary provided in
|
||
<previous-summary> tags.
|
||
|
||
update_user_message_suffix: |
|
||
Update the existing structured summary with new information. 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
|
||
|
||
Use this EXACT 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]
|
||
|
||
Keep each section concise. Preserve exact file paths, function names, and error messages.
|
||
|
||
update_user_message_prefix_zh: |
|
||
以上消息是需要整合到现有摘要中的新对话内容，现有摘要位于<previous-summary>标签中。
|
||
|
||
update_user_message_suffix_zh: |
|
||
用新信息更新现有的结构化摘要。规则：
|
||
- 保留来自先前摘要的所有现有信息
|
||
- 从新消息中添加新的进展、决策和上下文
|
||
- 更新进度部分：当完成时将项目从"进行中"移到"已完成"
|
||
- 根据已完成的内容更新"下一步"
|
||
- 保留确切的文件路径、函数名称和错误消息
|
||
- 如果某些内容不再相关，您可以删除它
|
||
|
||
使用此确切格式：
|
||
|
||
## 目标
|
||
[保留现有目标，如果任务扩展则添加新目标]
|
||
|
||
## 约束和偏好
|
||
- [保留现有内容，添加发现的新内容]
|
||
|
||
## 进展
|
||
### 已完成
|
||
- [x] [包含以前完成的项目和新完成的项目]
|
||
|
||
### 进行中
|
||
- [ ] [当前工作 - 根据进展更新]
|
||
|
||
### 阻塞
|
||
- [当前阻塞问题 - 如果解决则删除]
|
||
|
||
## 关键决策
|
||
- **[决策]**: [简短理由]（保留所有之前的内容，添加新的）
|
||
|
||
## 下一步
|
||
1. [根据当前状态更新]
|
||
|
||
## 关键上下文
|
||
- [保留重要上下文，如需要则添加新的]
|
||
|
||
保持每个部分简洁。保留确切的文件路径、函数名称和错误消息。
|