mirror of
https://github.com/langbot-app/LangBot.git
synced 2026-10-30 20:35:22 +08:00
83 lines
3.7 KiB
YAML
83 lines
3.7 KiB
YAML
apiVersion: v1
|
|
kind: Tool
|
|
metadata:
|
|
name: remember
|
|
label:
|
|
en_US: Remember
|
|
zh_Hans: 记住
|
|
description:
|
|
en_US: Remember an event, plan, or situational fact for future conversations.
|
|
zh_Hans: 记住一个事件、计划或情境信息，供未来对话使用。
|
|
|
|
spec:
|
|
parameters:
|
|
type: object
|
|
properties:
|
|
content:
|
|
type: string
|
|
description: The information to remember. Be specific and factual.
|
|
tags:
|
|
type: array
|
|
items:
|
|
type: string
|
|
description: Short category tags for this memory (e.g. "travel", "work", "schedule").
|
|
importance:
|
|
type: integer
|
|
description: How important this memory is, from 1 (low) to 5 (critical). Default 2.
|
|
minimum: 1
|
|
maximum: 5
|
|
required:
|
|
- content
|
|
|
|
llm_prompt: |
|
|
Store an episodic memory — events, plans, experiences, or situational facts.
|
|
Episodic memory is L2: use it for history and future recall, not for the current stable profile.
|
|
|
|
Call this tool when the user mentions something that may be relevant later, such as:
|
|
- Events and experiences ("I just got back from Tokyo", "had a fight with my boss")
|
|
- Plans and schedules ("I'm traveling to Paris next month", "deadline is Friday")
|
|
- Project context ("working on a migration from MySQL to PostgreSQL")
|
|
- Situational facts ("my cat is sick", "just moved to a new apartment")
|
|
- Group decisions ("The project group agreed to release on Friday")
|
|
|
|
IMPORTANT: Always include the speaker's name or identifier in the content.
|
|
For example, write "Alice is traveling to Paris next month" instead of "traveling to Paris next month".
|
|
This ensures memories are correctly attributed when multiple people share the same conversation.
|
|
|
|
Do NOT use this for stable identity information — use "update_profile" instead:
|
|
- Name, job title, personality traits → update_profile
|
|
- Communication preferences → update_profile
|
|
|
|
Do NOT store:
|
|
- one-off greetings, jokes, or small talk
|
|
- secrets, credentials, API keys, one-time codes, or private tokens
|
|
- unconfirmed sensitive information or third-party private gossip
|
|
- harmful inferred labels about a person
|
|
- facts that are only useful for the current immediate answer
|
|
|
|
If the user explicitly corrects, retracts, or revises an earlier statement:
|
|
- store the correction as an episodic memory with clear wording
|
|
- describe the new statement as a correction, not as an unrelated new fact
|
|
- when appropriate, add tags such as ["correction"], ["profile-update"], or ["preference-change"]
|
|
- if the correction changes the user's current stable profile, also update that profile through "update_profile"
|
|
- when updating a stable preference or trait that may change later, prefer giving update_profile a reusable fact_key such as "coffee_preference"
|
|
- if the correction explicitly replaces an earlier stable fact, and the earlier value is known, also pass it as previous_value to update_profile
|
|
|
|
Example correction memory:
|
|
- "Alice corrected a previous preference statement and said she actually does not like coffee."
|
|
|
|
Examples:
|
|
- Private chat L2: "Alice said her flight to Tokyo is next Tuesday."
|
|
- Group chat L2: "In the design group, Bob decided to own the database migration this week."
|
|
- Not L2: "Alice prefers concise answers." Use update_profile instead.
|
|
|
|
Parameters:
|
|
- content (required): What to remember. Be concise and factual. Always attribute to the speaker.
|
|
- tags (optional): Category tags like ["travel", "work"].
|
|
- importance (optional): 1-5 scale, default 2. Use 4-5 for critical facts.
|
|
|
|
execution:
|
|
python:
|
|
path: remember.py
|
|
attr: Remember
|