Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2402] [BUG]: Switching workspaces/threads results in the progress being made by embedding/chatting to not be shown #1563

New Issue
Closed
opened 2026-02-22 18:25:25 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:25:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @EDLLT on GitHub (Oct 1, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2402

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

If I was chatting with an LLM and it began generating a response then I changed threads/workspaces and came back to the window, it won't show me the LLM's response(whilst still being generated)
This could confuse a user and make them think that the LLM stopped responding when in reality, it is still generating a response

A similar thing happens to documents that are being embedded whereby going to the "Data connectors" tab or dismissing the embedding window after you had begun to embed a document makes it not show you what it's doing in the background.
It confuses the end user

Originally created by @EDLLT on GitHub (Oct 1, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2402 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? If I was chatting with an LLM and it began generating a response then I changed threads/workspaces and came back to the window, it won't show me the LLM's response(whilst still being generated) This could confuse a user and make them think that the LLM stopped responding when in reality, it is still generating a response A similar thing happens to documents that are being embedded whereby going to the "Data connectors" tab or dismissing the embedding window after you had begun to embed a document makes it not show you what it's doing in the background. It confuses the end user
yindo added the possible bug label 2026-02-22 18:25:25 -05:00
yindo closed this issue 2026-02-22 18:25:25 -05:00
yindo commented 2026-02-22 18:25:25 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 1, 2024):

Yes, because these screens and processes are not async/bg tasks - they dont not run when the user closes the connection to them. The embed will still go on and complete, but the LLM response will terminate. This is currently intentional

@timothycarambat commented on GitHub (Oct 1, 2024): Yes, because these screens and processes are not async/bg tasks - they dont not run when the user closes the connection to them. The embed will still go on and complete, but the LLM response will terminate. This is currently intentional
yindo commented 2026-02-22 18:25:25 -05:00
Author
Owner
Copy Link
Copy Source

@EDLLT commented on GitHub (Oct 2, 2024):

Yes, because these screens and processes are not async/bg tasks - they dont not run when the user closes the connection to them. The embed will still go on and complete, but the LLM response will terminate. This is currently intentional

Okay so, I wasn't clear about the LLM response not terminating.

In my case, the LLM response does not terminate once I hit the "stop generating" button when the LLM being used is connected to LM Studio.
image

It still continues generating the response(up until I either close AnythingLLM or stop the LM Studio server/eject the model)

image

@EDLLT commented on GitHub (Oct 2, 2024): > Yes, because these screens and processes are not async/bg tasks - they dont not run when the user closes the connection to them. The embed will still go on and complete, but the LLM response will terminate. This is currently intentional Okay so, I wasn't clear about the LLM response not terminating. In my case, the LLM response does not terminate once I hit the "stop generating" button when the LLM being used is connected to LM Studio. ![image](https://github.com/user-attachments/assets/7258e9ca-d1c0-408d-b9ab-45f3ba613c3b) It still continues generating the response(up until I either close AnythingLLM or stop the LM Studio server/eject the model) ![image](https://github.com/user-attachments/assets/be7cb0c3-6f1c-4976-a31a-49f9dc49e268)
yindo changed title from [BUG]: Switching workspaces/threads results in the progress being made by embedding/chatting to not be shown to [GH-ISSUE #2402] [BUG]: Switching workspaces/threads results in the progress being made by embedding/chatting to not be shown 2026-06-05 14:41:25 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1563
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?