NousResearch/hermes-agent

Dashboard chat stuck; fix for custom provider sessions

Cluster 108383. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

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

Read #110234 Pick up a Lab task

These items concern Dashboard /chat sessions failing to start (stuck on 'Setup Required' or queued indefinitely) when using custom endpoints or providers, while CLI works fine. Includes a reported fix allowing Dashboard chat to initialize correctly with custom providers.

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.

#110234 Dashboard /chat stops parking on Setup Required for custom endpoints; Desktop tab + on named local profiles keeps session controls (#108383, #108369, salvage #102840)

merged to main

files: apps/desktop/src/app/session/hooks/use-session-actions.test.tsx, apps/desktop/src/app/session/hooks/use-session-actions/index.ts, apps/desktop/src/app/session/hooks/use-session-actions/utils.ts, apps/desktop/src/store/session.ts, hermes_cli/auth.py, tests/hermes_cli/test_resolve_provider_custom_endpoint.py

1 PR closed without merging

From the close comments: done elsewhere 1

#108408 fix(gateway): let Dashboard chat start with custom providers · done elsewhere → 271515b, #108383, #107922, #107918

Closed issues · 1

Closed#108383Dashboard chat (/chat) sessions never go live: stuck "Setup Required"/queued forever, while CLI (hermes chat) works fine on same gateway

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.67: 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

Merged PRs: #110234
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 13 Sep 2026

For your agent

The same facts, typed.

cluster/108383.json
cluster/108383.md