Skip to content

[BUG] Desktop model selector remains empty after setup until frontend reload #1197

Description

@HarshaNethra

Description

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

  1. Install and launch the OpenJarvis desktop app on Windows.
  2. Allow the initial setup and backend startup process to complete.
  3. Open the model selector in the frontend and observe that no models are available.
  4. Attempt to send a message. The request may fail with "Error during generation: Model '' not found in any engine".
Image Image
  1. Reload the frontend with Ctrl+R.
  2. Observe that the models appear and chat works as attached.
Image Image

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.

Operating System

Windows

Python Version

3.13

Hardware

NVIDIA GPU

Engine

Ollama

Logs / Traceback

Activity

  1. HarshaNethra commented on Oct 27, 2026

    @HarshaNethra
    Author

    take

  2. added theissue type on Oct 28, 2026
  3. updated Priority P2 and Effort M on Oct 28, 2026
  4. moved this from To triage to Backlog in Issue Trackeron Oct 28, 2026
  5. moved this from Backlog to In progress in Issue Trackeron Oct 28, 2026
  6. SparTT commented on Oct 30, 2026

    @SparTT

    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

  7. HarshaNethra commented on Oct 31, 2026

    @HarshaNethra
    Author

    I verified the PR #1204 locally, and can confirm that the issue is resolved in my testing.
    Thanks for working on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

P2

Effort

M

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions