-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Idea] Button for Duplicate chat with answer beam (without closing the current beam window) #668
Comments
Great idea @darthalex2014. This is in addition to the change I made for "multi-part" Add To Chat, which is already very precious and you suggested: Tell me more about this request
|
Currently, we have Chat 1 open. In it, a beam search is running, which has produced 8 responses. |
@darthalex2014 something like this? Need to evaluate tradeoffs of the UI and implement the logic part. For reference, the following was the quick/dirty code hack:
|
yes! |
@darthalex2014 - this is a great idea. Done and works well, I see why you ask for it; it's great to fork-off variants to then re-explore. It's not available to the public yet as I'm preparing Big-AGI 2, but will be soon. Screenshot below, and it's working well. Let me know if you have other GREAT IDEAS! In addition, you also get a visual indication of the branch history & auto retitle, so it's easier to continue with the new train of thought. Works on both beams and merges. What's next @darthalex2014 ? |
Button for Duplicate chat with answer beam (without close current beam window)
During the generation of multiple answers in Beam, sometimes it's desirable to compare further chat responses with different Beam answers.
If you click "choose this message", it inserts one message into the chat and the beam window closes, and we lose all other answers.
I propose to create a "duplicate" button. This button would create a duplicate of the current chat and insert the selected beam answer into it, without closing the current window with all the beam answers.
The text was updated successfully, but these errors were encountered: