mudler / mudler/LocalAI

Agent response disappears when navigating away via "Status" or switching chats in chat section

Open
#11,702 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug unconfirmed
Dominant language
Go
Stars
49.2k
Forks
4.5k
Avg merge
1d 3m
Merged PRs (30d)
239

Description

LocalAI version:
7.9.0

Environment, CPU architecture, OS, and Version:
Linux Ubuntu

Describe the bug
Hi there,

I encountered an issue where the agent's response is lost if I navigate away while it is still thinking or generating text.

To Reproduce
Steps to Reproduce in Agents screen:

Start a conversation with an agent.
While the agent is processing (thinking) or streaming the response, click on the "Status" button in the top-right corner of the web UI.
Return to the conversation (or press back). The full response is not displayed, even if the generation has finished.

In Chat Mode:
If I switch to a different chat tab (in the same browser tab) while the model is reflecting or writing, and then return to the original chat, the response is missing if it had not finished writing yet.

I imagine these are limitations of the current web UI architecture that might be complex to fix with JavaScript. A potential workaround could be to move conversation-related functions (like the Status view) into popup windows. This would allow users to interact with these features without losing the context of the ongoing conversation.

Let me know if you need more details!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue from the Agents screen using the Status button, then in Chat Mode by switching chat tabs during generation. Trace how the active conversation and streamed response are handled across navigation; done means returning to either conversation shows the complete response after generation finishes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.