Reset flagged values when switching conversations in chat history

[abidlabs]

When both flagging (#10272) and chat history (#10191) are enabled, flagged messages are shared between conversations. E.g. if you flag the first message in one conversation, the first message appears to be flagged in all conversations.

This PR fixes that -- now the flagged values are saved as part of the chat history for each conversation separately reset. This PR also makes a few small tweaks to improve the UI/UX saving history and flagging:

• In ccb06da, I tweak the "new chat" logo
• In 498330f, I allow users to "unselect" a flagging option or like/dislike. Closes: Allow canceling the like/dislike status in gr.Chatbot #10286

---

For an example with only gr.Chatbot, try something like this:

import gradio as gr

with gr.Blocks() as demo:
    c = gr.Chatbot(
        value=[{"role": "user", "content": "Hello"}, {"role": "assistant", "content": "Hi"}, {"role": "user", "content": "Hello"}, {"role": "assistant", "content": "Go away"}],
        type="messages",
        feedback_options=["Like", "Spam", "Inappropriate", "Other"],
        feedback_value=["Like", "Other"],
    )
    c.like(lambda x: x, None, None)
    b = gr.Button("Clear flags")
    b.click(lambda: gr.Chatbot(feedback_value=None), None, c)

if __name__ == "__main__":
    demo.launch()

Or test the whole experience of switching between conversations using the demo/chatinterface_streaming_echo/run.py demo.

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
	Storybook	ready!	Storybook preview
🦄	Changes	detected!	Details

---

Install Gradio from this PR

pip install https://gradio-pypi-previews.s3.amazonaws.com/1485016253b16a502cd334c01d3e6aee37ba0aa2/gradio-5.9.1-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@1485016253b16a502cd334c01d3e6aee37ba0aa2#subdirectory=client/python"

Install Gradio JS Client from this PR

npm install https://gradio-npm-previews.s3.amazonaws.com/1485016253b16a502cd334c01d3e6aee37ba0aa2/gradio-client-1.8.0.tgz

Use Lite from this PR

<script type="module" src="https://gradio-lite-previews.s3.amazonaws.com/1485016253b16a502cd334c01d3e6aee37ba0aa2/dist/lite.js""></script>

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
@gradio/atoms	minor
@gradio/chatbot	minor
gradio	minor

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Reset flagged values when switching conversations in chat history

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[abidlabs]

orjson requires dictionaries to have str keys, otherwise serialization fails and the gradio app crashes.

[abidlabs]

Adds a self._id in case your Gradio app has multiple gr.ChatInterface-s

Suggested change

	[], storage_key=f"_saved_conversations_{self._id}"
	[], storage_key=f"_saved_conversations_{self._id}"

[abidlabs]

Decided to avoid using decorator syntax for consistency with the rest of the file

[aliabid94]

icon should be dark gray/black. orange loooks weird

[dawoodkhan82]

Tested and fixes the flagging issues.

[abidlabs]

@aliabid94 thoughts on changing to a primary button? like this:

[aliabid94]

Concern about storing flagged info in two different places (in csv, and in browser state) is that they may diverge. For example, a user may delete the csv to clear the flagging history, but it will still show up in the browser.

[abidlabs]

Synced with @aliabid94 about this:

Concern about storing flagged info in two different places (in csv, and in browser state) is that they may diverge. For example, a user may delete the csv to clear the flagging history, but it will still show up in the browser.

and decided to change this approach to reset the flagging values instead of preserving them in browser state. Simplifies the PR considerably.

[aliabid94]

LGTM!

[abidlabs]

Thanks @dawoodkhan82 @aliabid94 for the reviews!