[GH-ISSUE #1660] feat: persist model download status in Settings/Models #51248

New Issue

GiteaMirror · 2026-05-05T12:09:38-05:00

GiteaMirror commented

2026-05-05 12:09:38 -05:00

Originally created by @bkopec on GitHub (Apr 22, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1660

Is your feature request related to a problem? Please describe.
Model download status line doesn't persist when changing pages in settings.

Describe the solution you'd like
I believe the status should persist.

Originally created by @bkopec on GitHub (Apr 22, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/1660 **Is your feature request related to a problem? Please describe.** Model download status line doesn't persist when changing pages in settings. **Describe the solution you'd like** I believe the status should persist.

GiteaMirror closed this issue

2026-05-05 12:09:39 -05:00

GiteaMirror commented

2026-05-05 12:09:42 -05:00

@justinh-rahb commented on GitHub (Apr 22, 2024):

If you navigate away from the models modal, it will break the receiving of "Server Side Events" which tell the frontend of the current status of the download in the backend. If it's not shown, it's still happening in the background, and you can re-establish the sending of SSEs by putting the model name in again and clicking the download button, it will resume where it's currently at.

@justinh-rahb commented on GitHub (Apr 22, 2024): If you navigate away from the models modal, it will break the receiving of "Server Side Events" which tell the frontend of the current status of the download in the backend. If it's not shown, it's still happening in the background, and you can re-establish the sending of SSEs by putting the model name in again and clicking the download button, it will resume where it's currently at.

GiteaMirror commented

2026-05-05 12:09:43 -05:00

@bkopec commented on GitHub (Apr 23, 2024):

Isn't it bad design ?

The model download feature is core to new users, the download bar is important as they need to wait until it's achieved to start using the app, problem is the download takes time so user is tempted to explore around, and it's counter-intuitive that you have to "pull the model again" just to "view the download status bar".

@bkopec commented on GitHub (Apr 23, 2024): Isn't it bad design ? The model download feature is core to new users, the download bar is important as they need to wait until it's achieved to start using the app, problem is the download takes time so user is tempted to explore around, and it's counter-intuitive that you have to "pull the model again" just to "view the download status bar".

GiteaMirror commented

2026-05-05 12:09:44 -05:00

@justinh-rahb commented on GitHub (Apr 23, 2024):

Isn't it bad design ?

The model download feature is core to new users, the download bar is important as they need to wait until it's achieved to start using the app, problem is the download takes time so user is tempted to explore around, and it's counter-intuitive that you have to "pull the model again" just to "view the download status bar".

It is what it is. Short of re-architecting the frontend to spawn some sort of listening process in the background to listen for those server-side events, this is not currently acheivable. PRs more than welcome, always.

@justinh-rahb commented on GitHub (Apr 23, 2024): > Isn't it bad design ? > > The model download feature is core to new users, the download bar is important as they need to wait until it's achieved to start using the app, problem is the download takes time so user is tempted to explore around, and it's counter-intuitive that you have to "pull the model again" just to "view the download status bar". It is what it is. Short of re-architecting the frontend to spawn some sort of listening process in the background to listen for those server-side events, this is not currently acheivable. PRs more than welcome, always.

GiteaMirror commented

2026-05-05 12:09:45 -05:00

@tjbck commented on GitHub (Apr 23, 2024):

Could be an easy fix actually, using global store instead of component local variable might just do the job here. I'll see what can be done @bkopec.

@tjbck commented on GitHub (Apr 23, 2024): Could be an easy fix actually, using global store instead of component local variable might just do the job here. I'll see what can be done @bkopec.

GiteaMirror commented

2026-05-05 12:09:46 -05:00

@tjbck commented on GitHub (Apr 23, 2024):

@bkopec should be fixed on our dev branch, let me know if the issue persists :)

@tjbck commented on GitHub (Apr 23, 2024): @bkopec should be fixed on our dev branch, let me know if the issue persists :)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#51248