hermes - 💡(How to fix) Fix Desktop composer Enter key does not send message on Windows

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

This makes the primary desktop chat input feel broken because the normal keyboard send shortcut does not work on the initial single-line draft.

Fix Action

Fix / Workaround

A reliable workaround on this machine is:

RAW_BUFFERClick to expand / collapse

Bug description

On the Hermes Desktop app on Windows, pressing Enter in the main chat composer after typing text does not send the message.

A reliable workaround on this machine is:

  1. Type text in the desktop chat input/composer.
  2. Press Enter → nothing is sent.
  3. Press Shift+Enter to insert a newline.
  4. After that, sending becomes possible / the composer behavior changes enough to proceed.

This makes the primary desktop chat input feel broken because the normal keyboard send shortcut does not work on the initial single-line draft.

Steps to reproduce

  1. Open Hermes Desktop on Windows.
  2. Focus the main chat input/composer.
  3. Type a normal single-line message, for example hello.
  4. Press Enter.

Expected behavior

Pressing Enter should submit/send the current message from the main desktop chat composer, unless the app intentionally documents a different shortcut.

If Shift+Enter is the newline shortcut, then the expected behavior is usually:

  • Enter = send
  • Shift+Enter = newline

Actual behavior

Pressing Enter after typing text does not send the message.

On the affected Windows machine, the user must first use Shift+Enter to create a newline before the composer becomes usable for sending.

Notes / possible area to inspect

This appears related to desktop composer keyboard handling rather than the backend/gateway:

  • Desktop app package version in repo: apps/desktop/package.json0.15.1
  • Desktop uses React/Electron.
  • Search found keyboard handling in apps/desktop/src/app/desktop-controller.tsx, components/assistant-ui/*, and several onKeyDown handlers.
  • There may be a mismatch between the main composer’s intended submit shortcut and the multiline textarea/contenteditable behavior on Windows/Electron.

Environment

  • OS: Windows 10 / 10.0.26200
  • App: Hermes Desktop
  • Repo: NousResearch/hermes-agent
  • Package version observed locally: 0.15.1

Impact

High usability impact for Desktop users: the default chat input cannot be sent with the expected Enter key path, making first-time use look broken.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Pressing Enter should submit/send the current message from the main desktop chat composer, unless the app intentionally documents a different shortcut.

If Shift+Enter is the newline shortcut, then the expected behavior is usually:

  • Enter = send
  • Shift+Enter = newline

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING