Desktop new-chat first message requires double send
NousResearch/hermes-agent · cluster 62481 · apps/desktop
Data as of
Nothing open on GitHub. Fix merged in #71140. Check it covers your case.
The short answer
- Known?
- Yes. 16 related items grouped here, 7 issues already closed.
- Fix event
- A fix was merged to main in PR #71140. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple bug reports and fix attempts addressing a desktop issue where the first message in a new chat session fails to send on the first attempt — the input stays populated or the Enter key renames the tab instead of submitting. Several fix PRs target session initialization timing and a drift guard that aborts the first send.
Open issues0
Open PRs0
Fixes on record
-
#63624 fix(desktop): stop the submit drift guard from aborting every new chat
-
#71140 fix(desktop): never drop the first message in a new session (patient agent-build wait + error surfacing)
files:
apps/desktop/src/app/session/hooks/use-message-stream/agent-init-error.test.tsx,apps/desktop/src/app/session/hooks/use-prompt-actions/index.test.tsx,cli-config.yaml.example,contributors/emails/[redacted:email],contributors/emails/[redacted:email],hermes_cli/config.py,tests/test_tui_gateway_server.py,tui_gateway/server.py
7 PRs closed without merging
From the close comments: done elsewhere 4 · duplicate 2 · merged via another change 1
-
#62482 fix(desktop): re-baseline session-context drift after new-chat creation (#54527 regression) · duplicate →
#63624,#54527,#62481 -
#62562 fix(desktop): send first message in new sessions · merged via another change →
8c28876,#71140,#63078 -
#63358 fix(desktop): replay pending composer draft after bind · done elsewhere →
8b84d82,2afa92c,#63210 -
#63502 fix(desktop): re-baseline session-context drift after new-chat creation (#54527 regression) · duplicate →
#63624,#54527,#62481 -
#63584 fix(desktop): allow first message submit during new chat initialization · done elsewhere →
8c28876,#63574
Closed issues · 7
- Closed#62481Bug: new-chat first Enter requires a second press; prompt lands in title bar (#54527 regression)
- Closed#62501UX: First message in new conversation sets title instead of sending
- Closed#62569[Bug]: Hermes Desktop Require Sending Messages Twice
- Closed#63024Desktop: New session requires pressing Enter twice — first Enter renames tab, second executes
- Closed#63210[Bug]: Desktop composer not ready on new session — first Enter fails, message stays in input, needs second send
- Closed#63231Composer text not cleared after sending first message in a new conversation
- Closed#63574bug(desktop): First message in new chat not sent — stays in input field (Enter or Send button), second press works (Windows)
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.11: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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