Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Member
|
Hi @j-erler, thank you very much for this PR! Since #992 by @peerschuett also adds copying chats, we decided to continue with #992 and close this one. Your work still shaped the result: #992 now takes over two of your ideas. One is the copy button in the chat toolbar, which also keeps what you have typed so far. The other is asking for the name of the copy. The changelog credits you for both. We built on #992 because it also handles audio transcripts that were not sent yet, refuses to copy while a transcription is still running, and cleans up when the copy cannot be stored. The name question now lives in one shared place, so both ways of copying ask it the same way. Thanks again for your contribution! 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A chat can now be copied into a second one of its own, from the workspace tree next to renaming and deleting, and from the chat toolbar. AI Studio asks what the copy should be called and suggests the original's name with "(copy)" behind it, then opens the copy while the original stays as it was.
WorkspaceBehaviour.DuplicateChatAsync writes the chat out and reads it back instead of naming every field, so what survives a restart survives being duplicated. The files a chat owns are copied with it, because the transcripts of attached media live below the chat's own directory, and the attachment paths of the copy are rewritten to point there. Sharing those files would cost the copy its transcripts the day the original is deleted. Documents attached from elsewhere keep pointing at where they are.
The two entry points differ in one respect. From the tree, the stored chat is copied, and the usual question about unsaved changes comes first, because the copy is opened afterwards. From the toolbar, the chat is copied as it stands on the screen, including a message typed but not sent, so nothing is at risk and nothing is asked.
Tested manually: both entry points, the suggested name, the copy opening, and that writing in the copy leaves the original untouched. Untested for lack of such a chat: copying one with transcribed audio or video and then deleting the original.