How to keep a streaming response going when switching to another conversation?

[sebslight]

Question

When a reply is streaming and I click into a different conversation (navigate away), the generation stops. When I return to the original conversation, the partial response is frozen and I typically need to rerun the prompt.

Is there a built-in way or recommended configuration to keep generation streaming in the background while navigating across conversations/routes?
If not, is there a documented pattern (config flag, plugin, or deployment setting) that allows this behavior?

What I’m trying to achieve
• Start a long generation in Conversation A.
• Switch to Conversation B (or another route like Settings) to multitask.
• Come back later and see that Conversation A has continued generating (or finished) without me keeping that view open.

What I observe
• Navigating away seems to abort/close the in-flight stream tied to the original chat view.
• On return, the stream is no longer active and I need to resend the request.

What I’ve tried
• Reproduced in multiple browsers.
• Opening a second tab with Conversation B keeps Conversation A streaming in the first tab (workaround).
• Checked proxy/app timeouts to rule out server-side timeouts (issue appears specifically on route change, not just long durations).
• Looked for any setting related to “background streaming” or “keep generating after navigation,” couldn’t find one.

Specific questions
1. Is the interruption on route change expected behavior today?
2. Is there an environment variable, config option, or UI setting that allows streaming to continue across navigation?
3. Does any existing feature (e.g., multi-response modes) change this behavior, or is it strictly tied to the active chat view?
4. If there’s no out-of-the-box support, is there a recommended approach (client or server) to avoid aborting the stream on navigation?