NousResearch/hermes-agent

Desktop onboarding provider/model mismatch bug fix

Cluster 80762 · apps/desktop. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #115836 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #115836. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #115836. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #115836, then check it covers your case.

Read #115836 Pick up a Lab task

A bug in the desktop first-run onboarding flow causes a mismatch between the selected model and its provider when the default model is changed. The related issues and PRs address keeping the provider paired correctly with the chosen model during onboarding.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#115836 fix(desktop): onboarding model pick from another provider persists that provider and relabels the card (#80762, salvage #80775)

merged to main

files: apps/desktop/src/components/onboarding/flow.test.tsx, apps/desktop/src/components/onboarding/flow.tsx, apps/desktop/src/store/onboarding.test.ts, apps/desktop/src/store/onboarding.ts, contributors/emails/[redacted:email]

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

#80775 fix(desktop): persist onboarding model change against the picked model's provider · merged via another change → fbcc605, #115836, #80762, #80775
#81551 fix(desktop): keep onboarding provider paired with model (#80762) · duplicate

Closed issues · 1

Closed#80762[Bug]: Desktop first-run onboarding: changing the default model to one from a different provider writes a provider/model mismatch, chat errors "provider doesn't have the selected model"

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: apps/desktop
Merged PRs: #115836
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/80762.json
cluster/80762.md