AI chatbot sidebar should maintain conversation history across open/close cycles
Categories
(Core :: Machine Learning: General, enhancement)
Tracking
()
People
(Reporter: z11imdk, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0
Steps to reproduce:
- Open Firefox with AI chatbot feature enabled
- Open AI chatbot sidebar (via Ctrl+X shortcut on macOS or UI button)
- Have a multi-turn conversation with the chatbot
- Close the chatbot sidebar (via Ctrl+X on macOS or UI button)
- Reopen the chatbot sidebar
Actual results:
The chatbot sidebar opens with a fresh chat session. The previous conversation is completely lost.
Expected results:
The chatbot sidebar should preserve and restore the active conversation when reopened.
While other Firefox sidebars (bookmarks/history) may not preserve UI state, chat conversations are fundamentally different - they are stateful sessions with context that builds across multiple interactions. Losing conversation history when closing the sidebar makes the feature impractical for any workflow that requires switching focus between the chat and other browser activities.
Expected behavior: reopening the sidebar should restore the last active conversation, allowing users to continue where they left off.
Comment 1•9 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Machine Learning: General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•8 months ago
|
Additional report: LibreWolf Portable 152.0.2-1 (Firefox 152 ESR-based), Windows 11 24H2, AI Chat sidebar with Brave Leo provider.
On an unstable Wi-Fi connection (frequent transient drops of 2–10 s, sometimes much longer), the AI Chat sidebar session is lost on every drop. The conversation is not recoverable — no session ID is retained, no local persistence, no export. Frequency: ~10 lost conversations over 15 days, some within minutes of starting.
This makes the feature effectively unusable for anyone on an unreliable connection (rural areas, aging hardware, mobile hotspots). A brief network interruption should not destroy the entire conversation context. The conversation should not be blanked without allowing to save it first (ctrl-A+ctrl-C at least, or other).
Minimal fix: retain the provider's session/URL in the sidebar's internal state so that a network drop triggers a reconnect rather than a full reset.
Description
•