Official issues about the desktop application. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
The Desktop GUI spawns a new CLI process roughly every 10 seconds, each running a full plugin discovery cycle, causing excessive log output and unnecessary CPU/disk usage.
When a user points /model at a local loopback endpoint and exits the TUI uncleanly, the session's ended_at stays NULL, causing the next Desktop launch to synchronously retry the dead endpoint and block the backend event loop for 60-100+ seconds, producing a startup timeout.
On Windows, hermes desktop launches Electron as a child process inheriting the parent PowerShell console, so closing the parent shell kills the Desktop app, and child process logs (including garbled encoding errors) flood the user's terminal.
Umbrella feature request describing multiple subsystems (cron, dashboard, desktop) that don't properly support non-default Hermes profiles, since the codebase assumes ~/.hermes/ is the canonical root instead of consistently resolving ~/.hermes/profiles/<name>/.
Removing a composer attachment in Hermes Desktop only updates the in-memory store, not localStorage, so the attachment reappears after switching sessions and switching back.
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.
Operating a desktop app currently requires describing the window and controls in text; the proposal adds a way to attach a live window so the agent can see and control it via a UI-automation sidecar, already implemented per PR #53852.
User requests a font size adjustment option for the Hermes desktop app to improve readability for users with poor eyesight.
Requests enhancing the desktop/TUI pet display with a floating window, real-time execution status (current tool, progress, token usage), cross-agent reactivity, and more states, inspired by Petdex Desktop.
Requests adding volume, pause/resume, and playback speed controls to the desktop app's audio/TTS playback pill, which currently only offers a status label and a stop button.
After extensive investigation, the actual cause of desktop WebSocket loop stalls was found to be GIL contention from the Anthropic SDK's streaming consumer parsing thousands of SSE chunks, not the originally suspected busy-poll. This issue is now closed.
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.
When the Docker execution backend is selected in Hermes Desktop, there is no status indicator, no test-connection action, and no setup guidance if Docker Desktop is not installed or running, resulting in silent generic failures.
The desktop app's update screen shows only a few recent updates plus a count of remaining ones; the reporter requests a scrollable page listing all accumulated updates.
Switching models via the desktop chat model picker on Windows persists the change to the global config.yaml instead of scoping it to the current session, contrary to documented behavior.
After creating a worktree from the sidebar fork button, the session appears under both the new worktree group and the main group until the project view is re-entered.
The reporter states the application cannot be started after an update, with only a screenshot attached and no textual description.
This tracking issue consolidates roughly 25 reports of console windows (cmd, conhost, git, gh, powershell) flashing on the Windows desktop GUI when its windowless pythonw.exe backend spawns console-subsystem child processes without the no-window flag, and documents which spawn sites are still leaking based on source and git-history verification.
On the macOS desktop app, a non-default profile shows sessions, channels, and cron jobs belonging to the default profile: a cross-profile data leak in the UI.
This closed issue reported that Hermes Desktop builds fail again after code updates with an 'electronDist does not exist' error, because the update process clears the Electron binary cache, indicating the fix in PR #47276 was incomplete.
Desktop update on Ubuntu 26.04 failed at the vite build step and the desktop app could no longer start, while the CLI kept working. Closed.
Hermes Desktop GUI's frontend crashes with a tapClientLookup: Index out of bounds error and white-screens when tools like skill_manage, memory, or cronjob return an unexpected data structure.
The Kanban board is currently separate from the Desktop app, requiring users to run CLI commands and manually copy task IDs; the issue proposes integrating it via a sidebar or in-chat /kanban commands.
This issue reports that Hermes Desktop only supports setting a workspace directory at launch time via --cwd, making it inconvenient to work across multiple projects, and proposes per-session workspace selection inside the app.
Running hermes update or hermes desktop fails during the final Electron packaging stage; the reporter's title references a Windows desktop app, but the attached build log shows electron-builder packaging for macOS (darwin arm64).
The Hermes desktop app on macOS has no font size or zoom control, standard macOS zoom shortcuts and trackpad pinch don't work, and there is no config.yaml option; the issue requests adding one.
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 first-class client-only install mode for Hermes Desktop that connects to an existing remote Hermes instance, since today the app always attempts to bootstrap a local runtime on first launch unless one is found.
Hermes Desktop's Profiles page can list profiles but cannot actually switch which profile a connected remote backend uses; the issue requests a first-class profile switcher in the Desktop UI.
This issue requests a first-class remote-client onboarding flow in Hermes Desktop, so users with an existing Hermes backend can connect directly instead of being funneled into the local bootstrap/install flow.
This issue requests an official native mobile app for iOS and Android supporting real-time voice calling with the Hermes AI assistant.
Back to curated issues . School solution cards . Troubleshooting