Memory Chip

Concepts

The function of Memory Chips is to enhance the memory capacity of the Chatbot to some extent. The implementation involves creating Memory Chips for less frequently used background stories or non-critical character information. These Chips are temporarily inserted into the system prompt when triggered, and they are removed after one chat session to save context space.

Each Memory Chip consists of three fields:

1. Name: The name of the Memory Chip.

2. Content: The background story, non-important character information, or any other content you wish to store in the Chip.

3. Trigger Keywords (up to 5): When a message contains any of these keywords, the Memory Chip is triggered, and its content is inserted into the System Prompt for that chat session.

Example

To help you better understand the role of Memory Chips, consider the following example:

In this example, we're chatting with a Chatbot named Tim.

During our conversation, we mention John Doe, whom Tim has no prior knowledge of in his System Prompt or context.

Since John Doe may not be frequently discussed in our chats and storing his information permanently in the System Prompt would unnecessarily occupy context space, we can utilize a Memory Chip.

Now, I'm creating a Memory Chip called 'John Doe’s Info'.

Let's ask Tim if he knows about John Doe's information.

As you can see, Tim learned about John Doe's information through the content of the Memory Chip, and this information will be removed from the context after the conversation ends. This way, not only can the chatbot understand information outside the current context, but it also doesn't occupy space within the context.

---

Create Memory Chip

You can add or delete Memory Chips in the Memory Chip tab of the Chat Settings popup window.

PS:

1. Keywords are matched precisely, for example, "Johnny" will not trigger the keyword "John".

2. When multiple chips' keywords are triggered, multiple chips will be inserted into the context simultaneously.

3. Keywords are case-sensitive, so lowercase "john" will not trigger the keyword "John".