Downloading a conversation
Someone on the hub suggested the ability to download a conversation, which seems like a low hanging fruit. Opening the issue here so we keep track of it!
Someone on the hub suggested the ability to download a conversation, which seems like a low hanging fruit. Opening the issue here so we keep track of it!
It was me and I'm still in for it. Posted the discussion originally on huggingface.co due to, for me, this GitHub repo here being related to the UI app in general and at huggingface for their chat service specifically. Thank you opening the issue anyway. I appreciate your efforts.
edit: could be related so I'm referencing it here https://github.com/huggingface/chat-ui/pull/176
Haha nice, yeah it's a feature we would have to add to chat-ui to get it deployed on the hosted version.
As a workaround you can indeed download the prompt like so:
but it won't give you a clean history and you'd have to parse it (see sample response). I think it would be easy enough to add an endpoint to chat-ui for getting the conversation history in a structured way though.
Sample response:
{
"note": "This is a preview of the prompt that will be sent to the model when retrying the message. It may differ from what was sent in the past if the parameters have been updated since",
"prompt": "Below are a series of dialogues between various people and an AI assistant. The AI tries to be helpful, polite, honest, sophisticated, emotionally aware, and humble-but-knowledgeable. The assistant is happy to help with almost anything, and will do its best to understand exactly what is needed. It also tries to avoid giving false or misleading information, and it caveats when it isn't entirely sure about the right answer. That said, the assistant is practical and really does its best, and doesn't let caution get too much in the way of being useful.\n-----\n<|prompter|>How do I make a delicious lemon cheesecake?</s><|assistant|>To make a delicious lemon cheesecake, you can follow this recipe:\n\nIngredients:\n\n* 16 oz cream cheese, softened\n* 1/2 cup sugar\n* 3 large eggs, lightly beaten\n* 1 teaspoon vanilla extract\n* 1 tablespoon freshly squeezed lemon juice\n* 1/4 cup all-purpose flour\n* 1 pinch salt\n* Nonstick cooking spray\n* Fresh berries for garnish (optional)\n\nInstructions:\n\n1. Preheat your oven to 300°F (150°C). Grease a 9-inch springform pan with nonstick spray.\n2. In a medium bowl, mix together the flour and salt. Set aside.\n3. In a large mixing bowl, beat the cream cheese until smooth using an electric hand mixer. Add the sugar and continue beating until well combined.\n4. Beat in the eggs one at a time, making sure each egg is fully incorporated before adding the next. Stir in the vanilla and lemon juice.\n5. Gradually add the dry ingredient mixture into the wet ingredients while stirring on low speed. Be careful not to overmix.\n6. Pour the batter into the prepared pan. Tap the pan against the counter several times to release any air bubbles.\n7. Bake for 45-50 minutes or until the center of the cake is set. If necessary, cover the top of the pan loosely with foil during the last 15 minutes of baking to prevent excessive browning.\n8. Remove from the oven and allow the cake to cool completely at room temperature. Once cooled, transfer the cake to the refrigerator to chill for at least two hours before serving.\n9. When ready to serve, remove the sides of the springform pan and place the cake on a plate or platter. Garnish with fresh berries if desired. Slice and enjoy!</s><|prompter|>Thank you!</s><|assistant|>",
"model": "OpenAssistant/oasst-sft-6-llama-30b-xor",
"parameters": {
"temperature": 0.2,
"truncate": 1000,
"max_new_tokens": 1024,
"stop": [
"</s>"
],
"top_p": 0.95,
"repetition_penalty": 1.2,
"top_k": 50,
"return_full_text": false
}
}
You got it right, yes. My issue is targeting at a clean history download, including all messages shared. If my time spares me some hours, I'll put my hands on this myself. Until then we have this ticket.
Apologize for not responding to this open ticket for so long.
Due to the authors obviously "cooking something new"
https://huggingface.co/chat/tools
And also recommending more established chat ui solutions
https://huggingface.co/spaces/huggingchat/chat-ui/discussions/747
I probably won't consider contributing to this project anymore. That's why I would advise you @nsarrazin to close this ticket and the forum thread on huggingface now.
I'm excited what comes next and what you have in store for us!
If you plan to release a new solution and this solution is lacking a proper export function, I'm gonna think about opening a ticket for this again and/or also returning with a PR contribution myself.
Although I gotta disagree with you guys, @nsarrazin if you write something like this
Finally, chat-ui (the codebase powering HuggingChat) is still maintained (GitHub repo).
and if I look at the time span between your releases https://github.com/huggingface/chat-ui/releases and, for example, the not working chat link is throwing a
"502 Bad Gateway"
(This is the link: https://huggingface.co/chat
This link can be found here https://github.com/huggingface/chat-ui/blob/main/README.md and here https://huggingface.co/docs/chat-ui/index
And for documentation purposes a backup https://web.archive.org/web/20250430122159/https://huggingface.co/chat/)
I'm not quite sure if it makes sense to continue this project or maybe just abandon it and advise users (again) to use more matured solutions as already been proposed by @julien-c on your website.