Description
When renaming a conversation in the conversation history, the rename appears to succeed in the UI, but after refreshing the page, the conversation reverts to its previous name.
Steps to Reproduce
- Open the application and start or locate an existing conversation.
- Rename the conversation using the rename option in the UI.
- Confirm the rename — the new name is displayed correctly.
- Refresh the page.
- The conversation name reverts to the original name.
Expected Behavior
The new conversation name should persist after a page refresh.
Actual Behavior
The rename is only reflected in the UI temporarily. After refreshing the page, the conversation name reverts to the previous (original) name.
Impact
Users cannot reliably rename conversations, as any rename is lost on page refresh, making the feature non-functional.
Additional Context
This appears to be a bug in the conversation history persistence layer — the rename may not be saved to the backend (e.g., Cosmos DB) and only updates the local UI state.
Description
When renaming a conversation in the conversation history, the rename appears to succeed in the UI, but after refreshing the page, the conversation reverts to its previous name.
Steps to Reproduce
Expected Behavior
The new conversation name should persist after a page refresh.
Actual Behavior
The rename is only reflected in the UI temporarily. After refreshing the page, the conversation name reverts to the previous (original) name.
Impact
Users cannot reliably rename conversations, as any rename is lost on page refresh, making the feature non-functional.
Additional Context
This appears to be a bug in the conversation history persistence layer — the rename may not be saved to the backend (e.g., Cosmos DB) and only updates the local UI state.