You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Desktop model selector remains empty after setup until frontend reload #1197
On first launch of the OpenJarvis desktop app (I downloaded the "OpenJarvis_1.0.1_x64-setup.exe" in the latest release "Desktop desktop-v1.0.2"), the model selector can remain empty even after setup completes and the backend is running. Reloading the frontend with Ctrl+R makes the models appear, after which chat works normally.
The model-fetch effect in frontend/src/App.tsx runs on mount, while the desktop app is still displaying SetupScreen. If the request fails during startup, the error handler sets the models to an empty list. The effect has an empty dependency array, so it does not retry when setup finishes. basically, it appears to be a startup race between the frontend and backend.
I also verified that http://127.0.0.1:8000/v1/models returns the installed models once the backend is running. Reloading the frontend resolves the issue.
Steps to Reproduce
Install and launch the OpenJarvis desktop app on Windows.
Allow the initial setup and backend startup process to complete.
Open the model selector in the frontend and observe that no models are available.
Attempt to send a message. The request may fail with "Error during generation: Model '' not found in any engine".
Reload the frontend with Ctrl+R.
Observe that the models appear and chat works as attached.
Expected Behavior
The desktop app should load the available models once setup and backend initialization have completed. Users should not need to manually reload the frontend.
Actual Behavior
The initial model fetch appears to happen before the backend is ready. The fetch fails, and the frontend retains an empty model list after setup completes.
Activity
HarshaNethra commentedon Oct 27, 2026
take
SparTT commentedon Oct 30, 2026
Hi! I'm having the same issue too.
Besides reloading the UI, attempting to download any model seems to trigger a resync, causing the existing models to appear correctly.
My setup:
OpenJarvis Desktop 1.0.1
Python 3.11.0
Ollama
Model: qwen3.5:4b
HarshaNethra commentedon Oct 31, 2026
I verified the PR #1204 locally, and can confirm that the issue is resolved in my testing.
Thanks for working on this!