[GH-ISSUE #4836] [FEAT]: Branching threads when editing messages, collapsed thread-tree in sidebar #3045

Closed
opened 2026-02-22 18:32:23 -05:00 by yindo · 1 comment
Owner

Originally created by @til2000 on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4836

What would you like to see?

when I edit a message I want to be able to still have the past conversation flow available

there could be a thread parent in the sidebar (collapsed tree + icon) that unfolds and displays the tree structure of the branched conversations.

when I search for terms in the searchfield I'd like the thread parent to show up unfolded, with only the matching branches up to the message that includes the search term. any branch below that message shall be collapsed but available. branches unrelated to the search term shall not be displayed

Originally created by @til2000 on GitHub (Jan 8, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4836 ### What would you like to see? when I edit a message I want to be able to still have the past conversation flow available there could be a `thread parent` in the sidebar (collapsed tree + icon) that unfolds and displays the tree structure of the branched conversations. when I search for terms in the searchfield I'd like the `thread parent` to show up unfolded, with only the matching branches up to the message that includes the search term. any branch below that message shall be collapsed but available. branches unrelated to the search term shall not be displayed
yindo added the enhancementfeature request labels 2026-02-22 18:32:23 -05:00
yindo closed this issue 2026-02-22 18:32:23 -05:00
Author
Owner

@timothycarambat commented on GitHub (Jan 8, 2026):

The complexity required to support this architecture is quite significant if I understand it correctly.

Creating a new branch for every edit would likely crowd the sidebar UI and lead to a confusing "infinite fork" structure that is difficult to navigate since every edit makes a fork of a conversation.

For these concerns, I cannot see us supporting such a complex UX/UI request. If I am misunderstanding the requests please feel free to correct me on this

@timothycarambat commented on GitHub (Jan 8, 2026): The complexity required to support this architecture is quite significant if I understand it correctly. Creating a new branch for every edit would likely crowd the sidebar UI and lead to a confusing "infinite fork" structure that is difficult to navigate since every edit makes a fork of a conversation. For these concerns, I cannot see us supporting such a complex UX/UI request. If I am misunderstanding the requests please feel free to correct me on this
yindo changed title from [FEAT]: Branching threads when editing messages, collapsed thread-tree in sidebar to [GH-ISSUE #4836] [FEAT]: Branching threads when editing messages, collapsed thread-tree in sidebar 2026-06-05 14:50:00 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3045