[BUG] Response generation stops when navigating away from an active chat #109206

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When Claude is generating a response in an active conversation, navigating to another conversation or leaving the current chat appears to interrupt the ongoing generation.

After returning to the original conversation, the generated response is not restored, and Claude displays the following message:

"Checking for a response to your message. If Claude is still working on it, you'll see it here."

This creates an issue when users need to switch between multiple conversations while Claude is processing a request.

The generation state and response content do not appear to persist correctly across conversation navigation.

What Should Happen?

Response generation should continue in the background, independently of the currently active conversation.

Users should be able to navigate between multiple conversations without interrupting ongoing requests.

When returning to the original conversation:

• If generation is still in progress, its current status should be displayed.
• If generation is complete, the full response should be available.
• Previously generated content should not disappear.
• Conversation state should remain synchronized across navigation.

Error Messages/Logs

The following message appears when returning to the conversation:

"Checking for a response to your message. If Claude is still working on it, you'll see it here."

No additional error code or console logs have been collected.

Steps to Reproduce

1. Open Claude.ai in Google Chrome.
2. Start a new conversation.
3. Submit a prompt that requires a longer response.
4. Wait until Claude starts generating the response.
5. Before generation finishes, navigate to another conversation using the sidebar.
6. Wait briefly and return to the original conversation.
7. Observe the response generation status.
8. Notice that the original generation is not properly restored and the "Checking for a response" message appears.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

Not applicable – this issue was observed on Claude.ai web, not Claude Code.

Claude Code Version

Not applicable – this issue was observed on Claude.ai web, not Claude Code.

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Browser: Google Chrome

Interface: Claude.ai Web

Account plan: Free

This issue affects multitasking when users work with multiple conversations simultaneously.

Screenshot attached showing the "Checking for a response" message after navigating away from an active conversation and returning.

Suggested improvement: Implement persistent background response generation and conversation-state synchronization so that navigating between chats does not interrupt ongoing requests.