Switching chats during LLM response or tool call causes lost replies and aborted tool calls

[benverhees]

What happened?

When switching to another chat or creating a new chat while waiting for the LLM to reply, the response is not displayed in the UI when it completes. Similarly, when switching to another chat during an active tool call, the tool call gets aborted.

Version Information

Repository	Tag	Image ID	Created	Size
ghcr.io/danny-avila/librechat-dev	latest	11a3e817fe41	30 hours ago	1.75GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite	latest	fe4f4608cbf8	2 weeks ago	1.81GB
ghcr.io/librechat-ai/codesandbox-client/bundler	latest	569b08251638	3 weeks ago	207MB

Steps to Reproduce

For lost LLM replies:

1. Start a new chat in LibreChat
2. Send a prompt that will take some time to generate
3. While waiting for the response, switch to another chat or create a new chat
4. When switching back to the original chat, the LLM response is missing

For aborted tool calls:

1. Start a new chat in LibreChat
2. Send a prompt that requires tool usage
3. While the tool is executing (you can see the tool call in progress), switch to another chat
4. When returning to the original chat, observe that the tool call was aborted and no results are shown

What browsers are you seeing the problem on?

No response

Relevant log output

2025-05-27 10:40:06 warn: [OpenAIClient.chatCompletion][finalChatCompletion] Aborted Message
2025-05-27 10:40:06 warn: [OpenAIClient.chatCompletion][finalChatCompletion] API error
2025-05-27 10:40:06 error:
2025-05-27 10:40:45 info: [MCP][User: 68270ea4f4e68b63fe4435a8][tijd-en-datum] Establishing new connection
2025-05-27 10:40:46 error: [api/server/controllers/agents/client.js #sendCompletion] Operation aborted Aborted
2025-05-27 10:40:47 info: [MCP][User: 68270ea4f4e68b63fe4435a8][tijd-en-datum] Connection successfully established
2025-05-27 10:40:47 error: [MCP][User: 68270ea4f4e68b63fe4435a8][tijd-en-datum][get_current_time] Tool call failed This operation was aborted
2025-05-27 10:40:47 error: [MCP][User: 68270ea4f4e68b63fe4435a8][tijd-en-datum] Error calling "get_current_time" MCP tool: This operation was aborted

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Moved to feature requests & suggestions (not a bug).

This is intentional. Switching chats closes the connection, and the agent runs are setup to abort when the connection is closed.

Since some people prefer this not be the case, I'm thinking of adding a way to toggle the behavior, so that runs/messages can complete even when the connection is closed (but they would not be visible until complete)

[distardao]

@danny-avila I think running multiple requests simultaneously could affect the balance checking process. While one request is being processed, it might still be valid to create a new one, and when both requests are completed, the total token usage could exceed the balance, this could potentially cause a bug.

[benverhees]

Another solution could be, is to show a modal when the user tries to navigate away while a response is being generated. The modal could inform the user that continuing will abort the response, giving the choice to stay and wait or move away and abort.

[distardao]

My idea is to still allow the user to navigate to another conversation (for viewing or performing other activities). However, when the user attempts to create a new message, LibreChat will check if there is an active running request. If there is, a modal with a warning message will pop up, giving the user two options: either wait for the current process to complete or terminate it to create a new request. A URL to the previous active conversation will also be displayed in the modal for quick navigation.