Description:
Chat history edits are not being treated as a tree structure. When a message is edited, the system should auto-switch branches to reflect the new parent-child relationship, but currently the UI and API don't handle this properly.
Expected Behavior:
- When a message in the chat history is edited, the system should treat it as a new branch in the tree structure
- The UI should automatically switch to the new branch when the source changes
- Chat history sent to the API should reflect the tree structure properly
Current Behavior:
- Edits in chat history are not triggering branch switches
- The underlying system is built like a tree structure, but the UI and API layer don't implement this correctly
Notes:
This was a known issue during implementation but was not completed. The underlying data model supports tree structures, but the presentation layer and API communication layer need to be updated to properly handle branch switching when edits occur.
Description:
Chat history edits are not being treated as a tree structure. When a message is edited, the system should auto-switch branches to reflect the new parent-child relationship, but currently the UI and API don't handle this properly.
Expected Behavior:
Current Behavior:
Notes:
This was a known issue during implementation but was not completed. The underlying data model supports tree structures, but the presentation layer and API communication layer need to be updated to properly handle branch switching when edits occur.