The conversation summary is marginally useful the way it’s working. The biggest problem is that it doesn’t get the previous summary to work with, so when the conversation gets longer than its context window it becomes less than helpful as an add-on to the existing conversation.
My suggestions are:
1) The input should end with the last summary block. This way the AI can add onto that block and incorporate features from the beginning of the conversation as well.
2) The input should include the System Prompt because then it will know what it doesn’t have to put in the summary (any character detail that originated in the System Prompt can be left out.
3) The conversation summary should concentrate on the big “beats” of the conversation. It should look for big changes in the characters, emotional moments, promises given and fulfilled, identifying any new characters that were introduced.
4) The conversation summary should give the character creators a way to force certain things to be reflected in the summary. For example, if the character has defined “memory” saving commands (like “[MEMORY] This character is an ass.”) then the summary should keep any memory items that it can (possibly removing ones that are duplicates or were overridden). I tried using a construct like “(OOC: Summarizer, please include any [MEMORY] text in the summary as these are defined as data needing to be remembered.)” and it worked to some extent, but it could have been incorporated in the summary better.
Please authenticate to join the conversation.
New Submission
Feature Requests
API
About 2 months ago

omnius
Get notified by email when there are changes.
New Submission
Feature Requests
API
About 2 months ago

omnius
Get notified by email when there are changes.