Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partially disappearing chat (not sure what triggers it) #312

Open
mihai169 opened this issue Jan 27, 2025 · 1 comment
Open

Partially disappearing chat (not sure what triggers it) #312

mihai169 opened this issue Jan 27, 2025 · 1 comment
Assignees
Labels

Comments

@mihai169
Copy link
Collaborator

mihai169 commented Jan 27, 2025

Test case for acceptance criteria:

Scenario: Ensure the chat does not partially disappear
Given the user is actively using the chat feature
And the chat contains a series of messages
When the user performs any interaction with the chat
Then the entire chat history should remain visible
And no part of the chat should disappear unexpectedly

@snobbee
Copy link
Collaborator

snobbee commented Jan 30, 2025

@mihai169 We may need to reassess the architecture of the UI. At present, the conversation history is displayed by retrieving stored memories generated through interactions with Eliza. For custom actions such as those related to GitHub or Coinbase, we store the corresponding memories, allowing them to be retrieved, restored, and displayed in the Eliza UI. However, the built-in actions operate differently, as their responses such as "none" or "continue" are not stored as memories. Therefore when a user sends a message and receives a response, refreshing the page prevents those responses from being retrieved, resulting in gaps in the conversation history.

If any changes need to be made to address this issue, one possible approach would be to modify the system so that built-in action responses are also stored as memories, enabling their retrieval and proper display. Any modifications should be implemented in the upstream Eliza repository rather than our own, ensuring that improvements benefit Eliza as a whole rather than being limited to our specific plugins. This would provide a more maintainable and scalable solution while avoiding the need to manage separate, divergent versions of the core packages.

cc @jkbrooks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants