Load past conversations using the most recent leaf to determine the visible conversation tree. #1208

Activity

1. nsarrazin

   added

   enhancementNew feature or requestNew feature or request

   frontThis issue is related to the front-end of the app.This issue is related to the front-end of the app.

   on May 31, 2024
2. nsarrazin commented on May 31, 2024

   

   nsarrazin

   on May 31, 2024

   Last edited by nsarrazin

   Contributor

   More actions

   I think we could use sveltekit snapshots to store the bottom leaf and use that information to display the correct subtree when the user navigates back. Shouldn't be too hard
3. nsarrazin

   added

   good first issueGood for newcomersGood for newcomers

   on May 31, 2024
4. SvCy commented on Jun 7, 2024

   

   SvCy

   on Jun 7, 2024

   More actions

   Not essentially the newest/latest leaf based on generation but i think it should be the last "selected" leaf/branch.
   Either way, this shall also fix/relate to the issue here:
   Deleting a branch seems to refresh the entire chat-ui, thus resetting the chat back to branch 1. (as page reload does)

   And here's a possible solution I originally thought of (if even): adding route/chat order memory in User-Assistant/prompt-response rotation. eg. like sys prompt stored in each chat, the order of the last selected route will be stored as well.
   e.g. p1.r2.p1.r1.p5.r3 sequence. As there should already be a number system for re-ordering after branch deletion, to be merged with that.
   If a leaf/branch is deleted it can only change one unit rather then refreshing the enitre chat/chat-ui.

   		(p1).p2.p3.p4
   	     r1.(r2).r3
   		(p1)
   		(r1)
       p1.p2.p3.p4.(p5)
   	  r1.r2.(r3).r4.r5
   

   👍React with 👍1Reacted by Christoph J. Scherr
5. PlexSheep commented on Jul 6, 2024

   

   PlexSheep

   on Jul 6, 2024

   More actions

   This would be very helpful I think. I have a longer chat with a few branches, and currently I have to either select the right prompt and response (which are becoming more and more of course), or delete the branches that I don't end up using, which takes a long time and is tedious.

   I think that using the last selected would be most ergonomic, but we'd need to store what the last selected version was. Just using the latest would already help a lot.