Desktop: discovered_repos cache leaks across all profiles
Desktop's filesystem scanner broadcasts all discovered git repos to every profile's database due to a replace=True handler, so switching profiles shows repos belonging to other profiles.
Official issues about the terminal UI. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
Desktop's filesystem scanner broadcasts all discovered git repos to every profile's database due to a replace=True handler, so switching profiles shows repos belonging to other profiles.
The request asks for Claude Code-style mouse support (cursor placement, expandable sections, scrolling) and auto-copy of selected text to the clipboard in the Hermes CLI/TUI.
Requests live status indicators (spinners, watch mode, heartbeat display) for kanban tasks in the TUI/CLI, since current output is static and requires manual re-running to see progress.
The context-window usage gauge in the desktop/TUI status bar only refreshes on message.complete, so it stays frozen during long agentic turns even though the underlying data updates after every internal API call.
The /agents TUI panel stayed stuck on 'running' after subagents finished. Closed.
The Desktop app's Update button sometimes shows a manual 'run hermes update from terminal' dialog instead of updating directly, because resolveUpdaterBinary() fails to find hermes-setup.exe after a CLI-based rebuild that doesn't recopy it.
The request asks for a browser-style Ctrl+F/Cmd+F find UI in Hermes Desktop that can search chat transcripts and editor/settings panels with match highlighting and navigation.
Resuming any older chat in the Hermes desktop or TUI app fails with "No LLM provider configured" even though the default provider is valid and new chats work fine, while the identical session resumes correctly via the CLI's --resume flag.
Hermes Desktop only has partial UI support for custom OpenAI-compatible providers, forcing users to overload another provider's fields or manually edit config files; the issue requests a proper Custom provider row needing only a Base URL and API key.
This issue reports that Hermes Desktop's fixed-width chat container is impractical on both large monitors and small screens, and requests configurable text scaling and container width settings.
In Hermes Desktop, updating the Working Directory setting does not take effect for new sessions if the renderer's localStorage already has a remembered workspace cwd, so new sessions keep starting in the old directory despite config.yaml being updated correctly.
This issue requests a real-time voice conversation mode for Hermes Agent's terminal/TUI, including microphone input, streaming speech-to-text, low-latency responses, and streaming text-to-speech output.
On macOS in --tui mode, the gateway repeatedly exits mid-conversation with "stdin EOF (TUI closed the command pipe)" even with only built-in memory enabled (no byterover), which the reporter notes is distinct from a similar SIGPIPE issue (#14036) caused by the byterover memory plugin.
Starting the Docker image with HERMES_UID/HERMES_GID and a shared volume causes permission-denied errors when using the Chat feature in the web Dashboard. Issue is closed as fixed.
In the official Hermes Docker image, the dashboard's Chat tab fails on first connection because it runs as the unprivileged hermes user while /opt/hermes/ui-tui/ is root-owned, causing esbuild to fail writing the TUI bundle with EACCES.
hermes --tui can still display corrupted or stale glyphs after rapid terminal window resizing, a recurrence of the resize-desync class of issue previously addressed in #14640.
This issue proposes adding Shift+Enter as an additional newline keybinding in the Hermes CLI/TUI input, alongside the existing Alt+Enter and Ctrl+J bindings. This issue is closed.
Back to curated issues . School solution cards . Troubleshooting