[Bug] Unable to edit Assistant Information

[Ebcolan]

📦 Platform

Official Preview

📦 Deploymenet mode

client db (lobe-chat image)

📌 Version

Latest

💻 Operating System

Windows

🌐 Browser

Edge

🐛 Bug Description

Every time I edit the assistant information, through AI or personally, it doesn't save the settings and reverts back to the default assistant settings. The edits and changes made in session settings do not reflect on the chat assistant. The role settings however are saved and functioning, only the name of the assistant, tags, avatar, description, etc. are not changed from the default assistant settings.

📷 Recurrence Steps

1. Create new assistant.
2. Edit role settings.
3. Go to session settings
4. Auto generate assistant information
5. (No save button?) Exit the session settings.
6. Changes do not reflect.

🚦 Expected Behavior

The name, avatar, greeting should change in the assistant chat window since I've edited the assistant information in the session settings. This does not happen, and the assistant information reverts back to the default assistant settings.

📝 Additional Information

No response

[lobehubbot]

👀 @Ebcolan

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

The issue you're experiencing seems to be related to the saving mechanism for assistant information in the session settings. Here are a few things to consider:

1. Save Mechanism: It appears there might be no explicit save button in the session settings, which could be causing the changes not to persist. Ensure that there is a mechanism to save changes before exiting the session settings.

2. Validation Requirements: Make sure that all required fields such as name, description, and tags are filled out. The system requires these fields to be completed for the information to be saved successfully ^[1].

3. Client DB Mode: Since you're using the client db deployment mode, verify that the client-side state management is correctly synchronizing with the database. There might be an issue with how the state is being updated or saved.

4. Error Handling: Check if there are any error messages or logs that could provide more insight into why the changes are not being saved. This might help identify if there's an underlying issue with the saving process.

If these steps don't resolve the issue, it might be necessary to look into the codebase to ensure that the functions responsible for saving the assistant information are being called correctly and that there are no bugs in the implementation.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[dosubot]

The issue you're experiencing, where changes to the assistant information are not being saved and revert to default settings, might be related to a known problem that was addressed in previous updates. Specifically, there was an issue where assistant settings would reset to defaults, which was resolved in version 1.60.4. If you are not on this version or later, updating might resolve the issue.

Additionally, the assistant information is saved on the "blur" event, meaning changes should be saved when you click away from the input fields. If this is not happening, it could indicate a bug or a problem with the event listener not triggering correctly.

If you are already on the latest version and the problem persists, it might be worth checking if there are any specific configurations or browser settings that could interfere with the saving process. Also, ensure that the client database is correctly configured in the lobe-chat image, as this could affect data persistence.

If none of these solutions work, it might be necessary to look into the codebase for any recent changes that could have introduced this issue or to check for any open issues in the repository that might be related.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}