Issues labeled P1 by the maintainers, mostly known issues without a fix yet. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
Context compression could orphan tool messages by dropping their assistant tool_calls message, causing HTTP 400 on strict providers like DeepSeek. Closed.
The Telegram reconnect handler's updater.stop() call has no timeout, so when the underlying TCP socket is stuck in CLOSE-WAIT the polling task never wakes up, permanently blocking reconnect attempts and silently dropping messages for hours until a manual restart.
The Telegram gateway adapter hangs indefinitely at connect attempt 1/8 with the 30s asyncio.wait_for timeout never firing, but only under s6-overlay supervision per the reporter's diagnostics.
The trajectory compressor produces invalid message sequences with orphaned tool messages after context compaction, permanently breaking long-running sessions with a DeepSeek API 400 error.
AsyncSessionDB wraps SessionDB methods as async coroutines, but slash_commands.py calls them without await, causing /resume to crash with a TypeError. This issue is now closed.
The built-in Anthropic OAuth token exchange fails with HTTP 404 because Anthropic now blocks any request carrying a claude-cli/ User-Agent prefix regardless of version, confirmed by testing multiple User-Agent strings.
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.
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.
The Windows installer script has a parameter conflict on bare invocation. Labeled P1, meaning it blocks installation with no official workaround yet.
The official v0.15.0 Docker image fails to start with exit code 127: two init scripts (stage2-hook.sh, main-wrapper.sh) present in source but missing from the built image, plus a reference to the hermes_cli.container_boot module that was removed in the v0.15.0 refactor. Issue is closed as fixed.
Switching to gpt-5.5 via the OpenAI Codex provider (subscription OAuth) crashes on the first user message with "Non-retryable error (HTTP None): 'NoneType' object is not iterable," though fallback then takes over.
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.
The Matrix/Synapse gateway in the official Docker image breaks after a certain build, with startup logs stalling at 'fixing ownership :1000'; the bot can still send messages but does not respond to channel prompts. Issue is closed as fixed.
All calls to MiniMax-M2.7 and kimi-k2.6 (32,768 token context) were rejected by Hermes Agent's 64K minimum context check, taking down the Telegram bot and cron jobs even though the models previously worked without any config changes.
The reporter describes a Matrix gateway deployment fronting a custom LLM dispatcher that routes requests between local and cloud models per rule, and reports there is no in-band channel for per-message routing decisions (like a user's /model command) to reach that downstream dispatcher.
With a valid Claude Max 20x OAuth access token, every Hermes request to the native Anthropic provider fails with HTTP 400, reporting that extra usage has been exhausted. Issue is closed as fixed.
OpenAI Codex OAuth works via CLI, but the Telegram gateway reports 'No Codex credentials stored' despite the same credentials being valid, in a Docker/Coolify deployment. This issue is now closed.
On a fresh Hermes install (WSL2 Ubuntu), all OpenRouter model calls return HTTP 400 and hermes doctor reports the same, even though curl with the identical API key gets a valid response.
Starting hermes chat prints a welcome message and a notice that the tirith security scanner is unavailable, then immediately crashes with a traceback showing an asyncio selector KeyError followed by an unhandled exception in main.py. Issue is closed as fixed.
Back to curated issues . School solution cards . Troubleshooting