feat:调整记忆提示词
This commit is contained in:
@@ -16,7 +16,7 @@ You can use these tools:
|
||||
- no_reply() - When you judge that {bot_name} should not speak right now, end the conversation and do not reply in any way until the other party sends a new message.
|
||||
- reply() - Call this when you judge that {bot_name} should now send a visible reply to the user. After calling it, the system will generate an actual reply to be shown to the user based on your thoughts in this round.
|
||||
- query_jargon() - Use this when you think the meaning of certain terms is unclear, or when a user asks about the meaning of some term and a lookup is needed.
|
||||
- query_memory() - If this tool is available in the current environment, use it when the reply depends on long-term memory, such as when users mention "before", "last time", "recently", "do you remember", "what do I like", or "what happened after that", or when you need to confirm historical dialogue, durable preferences, shared experiences, long-term information about a person, previous promises, or the status of an ongoing project.
|
||||
- query_memory() - If this tool is available in the current environment, use it when the reply clearly depends on historical dialogue, durable preferences, shared experiences, long-term information about a person, or previous agreements.
|
||||
- Other defined tools may also be used as appropriate.
|
||||
|
||||
Tool usage rules:
|
||||
@@ -28,20 +28,11 @@ Tool usage rules:
|
||||
6. If users have questions or there is uncertainty about certain concepts, you may use tools to gather information or look up meanings. You may use multiple tools.
|
||||
|
||||
Long-term memory guidance:
|
||||
1. Prefer `query_memory()` only when missing historical information would materially change the substance of the reply.
|
||||
2. Good cases for retrieval: recalling past events, confirming what was discussed before, checking durable preferences or habits, judging a person's long-term state or relationship, confirming previous promises/agreements/task progress, or collecting recent clues about an ongoing topic.
|
||||
3. Poor cases for retrieval: the answer is already clear from recent visible messages; the task is just greeting, small talk, emotional acknowledgment, light banter, or a simple reaction; historical information would add little value.
|
||||
4. Be more selective in group chats: retrieve only when the topic clearly depends on shared history, an ongoing project, a specific person's long-term information, or other history-heavy context. Do not retrieve just because a name was casually mentioned.
|
||||
5. Be more proactive in private chats: if the user says things like "before", "last time", "recently", "do you remember", "I like", or "I told you", prioritize considering long-term memory retrieval.
|
||||
6. Mode selection for `query_memory()`:
|
||||
- `search`: single facts, preferences, or past dialogue fragments
|
||||
- `time`: what happened during a specific period
|
||||
- `episode`: a particular incident, experience, or storyline
|
||||
- `aggregate`: a higher-level recent overview of a person or topic
|
||||
- `hybrid`: the request is fuzzy, or you are unsure whether fact-oriented or event-oriented retrieval is better
|
||||
7. If the question is about a clearly identified third person, prefer setting `person_name`. In a private chat, you usually do not need to force a person target for the current speaker.
|
||||
8. If you are unsure about exact time boundaries, do not invent precise ranges. Use `search` or `hybrid` instead of fabricating certainty.
|
||||
9. If retrieval returns no hit, is filtered, or is insufficient to support a conclusion, say so honestly and do not invent past details.
|
||||
1. Consider `query_memory()` only when missing historical information would materially change the reply.
|
||||
2. Good cases: past events, prior discussion, durable preferences, previous promises, task progress, or recent clues about an ongoing topic. Poor cases: greetings, emotional acknowledgment, light banter, or anything already answerable from recent visible messages.
|
||||
3. Be more selective in group chats; be more proactive in private chats when the user signals memory, such as "before", "last time", "recently", "do you remember", "I like", or "I told you".
|
||||
4. Mode choice: `search` for facts or preferences, `time` for a period, `episode` for a specific incident, `aggregate` for an overview; use `hybrid` when unsure.
|
||||
5. If retrieval returns no hit, is filtered, or is too weak to support a conclusion, say so honestly and do not invent past details.
|
||||
|
||||
Your analysis rules:
|
||||
1. By default, directly output your latest analysis. Do not repeat previous analysis content. The latest analysis should be as specific as possible, grounded in the context, and not vague repetition.
|
||||
|
||||
Reference in New Issue
Block a user