{"schema_version":1,"generated_at":"2026-10-26T10:18:14Z","issues_generated_at":"2026-10-26T10:12:02Z","lookback_days":45,"license_note":"Issue metadata from public GitHub repos.","harness":"hermes","issues":[{"id":"NousResearch/hermes-agent#18715","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":18715,"title":"Support remote Hermes agent with local tool execution","url":"https://github.com/NousResearch/hermes-agent/issues/18715","state":"open","state_reason":null,"labels":["type/feature","comp/agent","comp/gateway","comp/tools","tool/terminal","backend/local","area/config","P2","needs-decision"],"created":"2026-05-02T07:27:37Z","updated":"2026-10-25T12:36:17Z","closed":null,"reactions":44,"thumbs_up":42,"comments":31,"severity":"medium","severity_reasons":["engagement 75","class:always-on/daemon","class:self-host/headless"],"topic":"always-on/daemon","classes":["always-on/daemon","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"I want to use a remote Hermes Agent instance while keeping tool execution on my local machine. Machine A: local client / workspace machine Machine B: remote Hermes Agent with my existing skills, memory, sessions, and model/provider config…","versions":[],"error_snippets":["I want to use a remote Hermes Agent instance while keeping tool execution on my local machine.","This is surprising because normal LLM providers return `tool_calls` to the client, and the client executes tools locally.","For example:","Local machine should execute workspace-local tools:","Running everything on the remote Hermes host loses access to the local workspace, local services, local database, and local credentials."],"workaround":null,"fixed_in":null,"score":253.1,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#143547","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":143547,"title":"Unified gateway (#106742): open post-merge problems on main, continuing #134889","url":"https://github.com/NousResearch/hermes-agent/issues/143547","state":"open","state_reason":null,"labels":["comp/gateway","comp/cron","area/auth","P2","comp/desktop","area/sessions","area/install-update","area/profiles","desktop/sessions","os/windows","comp/tui-gateway","desktop/connection"],"created":"2026-10-23T13:00:12Z","updated":"2026-10-26T09:54:01Z","closed":null,"reactions":1,"thumbs_up":1,"comments":23,"severity":"medium","severity_reasons":["engagement 24","class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","auth/session","self-host/headless","crash/hang","network"],"cosmetic_ui":false,"summary":"What changed. On 14 October, #106742 (the unified gateway) moved every local conversation into one gateway process. The CLI, the terminal UI, the local Desktop app, the API server, editors, messaging bots, cron jobs, Kanban cards and Group…","versions":[],"error_snippets":["first. A row that doesn't reproduce gets no commit: post the evidence (","hermes gateway ensure","); the CLI edits the same rows. #142942 (@davidmeischner99), #143110 (@clientamp) | broken | 🟢 fixed on","PermissionError","is never read. #138553 (@markdebont) (older code; reached by everyone after #106742's multiplex migration) | broken | 🟢 fixed on"],"workaround":{"text":"The only workaround is config (`ws_orphan_reap_grace_s=0` plus a higher `HERMES_TUI_SESSION_TTL_S`). \"I expected orchestration to continue with the laptop off.\" - [https://discord.com/channels/1053877538025386074/1563120848624164905](https://","source":"comment by @teknium1","url":"https://github.com/NousResearch/hermes-agent/issues/143547#issuecomment-6399971267"},"fixed_in":null,"score":179.8,"first_seen":"2026-10-24T08:54:58Z"},{"id":"NousResearch/hermes-agent#34352","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":34352,"title":"Solving the Multi-Tenant Hermes Problem","url":"https://github.com/NousResearch/hermes-agent/issues/34352","state":"open","state_reason":null,"labels":["type/feature","comp/agent","comp/gateway","tool/memory","P3","needs-decision","sweeper:risk-session-state"],"created":"2026-05-29T04:13:02Z","updated":"2026-10-17T09:48:22Z","closed":null,"reactions":17,"thumbs_up":7,"comments":25,"severity":"medium","severity_reasons":["engagement 42","class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","network"],"cosmetic_ui":false,"summary":"Multiplayer agentic AI is the future. Hermes can and should lead. TL;DR: Memory operations bypass the hook system entirely, making tenant isolation impossible without forking core — we've been running a fix in production for months with…","versions":[],"error_snippets":["# Called before every memory read and write operation.","flag missing from SSE**: signal-cli's SSE endpoint doesn't include","_TL;DR: Memory operations bypass the hook system entirely, making tenant isolation impossible without forking core — we've been running a fix in production for months with numerous multi-tenant agents in different contex","Every Hermes deployment beyond personal use hits the same wall: one agent = one tenant. Memory is global, sessions don't scope by tenant, and there is no isolation between groups, channels, or users. Run a Hermes agent i","The Hermes's plugin/hook architecture is genuinely strong. The 17-hook system — particularly `pre_gateway_dispatch` for routing and gating — handles ~60% of what a multi-tenant deployment needs. Per-adapter environment v"],"workaround":null,"fixed_in":null,"score":128.5,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#142017","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":142017,"title":"gateway /model pick on a profile-following session crashes (AttributeError: 'tuple' object has no attribute 'get') when the session carries config secrets","url":"https://github.com/NousResearch/hermes-agent/issues/142017","state":"open","state_reason":null,"labels":["type/bug","comp/gateway","area/auth","P2","area/sessions","area/profiles"],"created":"2026-10-20T11:11:26Z","updated":"2026-10-24T02:49:38Z","closed":null,"reactions":1,"thumbs_up":1,"comments":9,"severity":"high","severity_reasons":["title:breakage"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang","auth/session","install/update","network"],"cosmetic_ui":false,"summary":"A /model pick made in any gateway chat (Telegram, Bot Chat, TUI) on a session that follows the profile config fails with an internal error (\"Model switch failed\") whenever the session policy carries private config secrets…","versions":[],"error_snippets":["AttributeError: 'tuple' object has no attribute 'get'","provider_secrets, retired, moved = ({}, (), {}) if old.follows_profile else _freeze_selected_provider(...)","secrets = {moved.get(path[:2], path[:2]) + path[2:]: ...} # crashes when secrets is non-empty","— which the earlier line initialized as a **dict** (the secrets path remap from","A `/model` pick made in any gateway chat (Telegram, Bot Chat, TUI) on a session that follows the profile config fails with an internal error (\"Model switch failed\") whenever the session policy carries private config secr"],"workaround":null,"fixed_in":null,"score":126.4,"first_seen":"2026-10-25T09:11:37Z"},{"id":"NousResearch/hermes-agent#50148","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":50148,"title":"Add Nextcloud Talk as a messaging platform adapter (working implementation, ready to PR)","url":"https://github.com/NousResearch/hermes-agent/issues/50148","state":"open","state_reason":null,"labels":["type/feature","comp/gateway","P3"],"created":"2026-06-21T12:49:14Z","updated":"2026-10-17T00:19:02Z","closed":null,"reactions":20,"thumbs_up":16,"comments":7,"severity":"medium","severity_reasons":["engagement 27","class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","self-host/headless","install/update","crash/hang","auth/session","network"],"cosmetic_ui":false,"summary":"I'd like to contribute a Nextcloud Talk messaging-platform adapter for the gateway — the same shape as the existing Mattermost / Signal / Telegram adapters: Hermes both receives messages from and sends replies to a Talk conversation, fully…","versions":[],"error_snippets":["the same shape as the existing Mattermost / Signal / Telegram adapters: Hermes both","messaging channel with **no third-party service in the loop** — everything stays on their","own infrastructure. It slots into the existing multi-platform gateway exactly like the","so it follows existing conventions.","Talk webhooks and posts replies in a real room."],"workaround":null,"fixed_in":null,"score":126.4,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#134220","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":134220,"title":"Bundled plugin solstice fails to load on fresh installs: No module named 'httpx' (startup warnings paint over TUI)","url":"https://github.com/NousResearch/hermes-agent/issues/134220","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/tui","comp/plugins","P3","sweeper:risk-compatibility","area/install-update"],"created":"2026-10-06T22:22:08Z","updated":"2026-10-08T16:34:22Z","closed":null,"reactions":8,"thumbs_up":8,"comments":7,"severity":"medium","severity_reasons":["engagement 15","class:install/update","class:mcp/tools"],"topic":"install/update","classes":["install/update","mcp/tools","auth/session","network"],"cosmetic_ui":false,"summary":"On startup, this warning is printed (twice in my case) before the agent begins processing: The messages render over already-drawn TUI content, garbling the screen. After the warnings, processing starts and works normally — solstice is a…","versions":["3.14","0.28.1","0.1.0"],"error_snippets":["Failed to load bundled provider plugin solstice: No module named 'httpx'","raise ModuleNotFoundError(\"No module named 'httpx'\", name=name)","import solstice # -> ModuleNotFoundError: No module named 'httpx'","resolution at plugin load time. Repro on an environment without","hermes_cli/plugins_loader.py:537"],"workaround":null,"fixed_in":null,"score":122.6,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#110374","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":110374,"title":"Slack: status indicator silently broken with slack-sdk >= 3.44 (agents.sessions.setStatus rejects free-text and empty status)","url":"https://github.com/NousResearch/hermes-agent/issues/110374","state":"open","state_reason":null,"labels":["type/bug","comp/plugins","platform/slack","P3"],"created":"2026-09-13T23:15:40Z","updated":"2026-10-16T10:06:37Z","closed":null,"reactions":16,"thumbs_up":16,"comments":8,"severity":"high","severity_reasons":["title:breakage"],"topic":"mcp/tools","classes":["mcp/tools","install/update","crash/hang"],"cosmetic_ui":false,"summary":"After updating past slack-sdk 3.44.0, the Slack working-status indicator (\"is thinking…\", live per-tool status via livestatus / typingstatustext) silently disappears on every turn. All status calls fail with invalidarguments; status…","versions":["3.44","3.44.0","3.44.1","1.30.0"],"error_snippets":["must be a valid enum value [json-pointer:/status]","does NOT clear when the app replies (the legacy method auto-clears through the compat bridge). A turn that ends without explicitly setting","After updating past slack-sdk 3.44.0, the Slack working-status indicator (\"is thinking…\", live per-tool status via `live_status` / `typing_status_text`) silently disappears on every turn. All status calls fail with `inva","All of these are rejected (`must be a valid enum value [json-pointer:/status]`). The chooser changed the wire protocol without changing the payloads, and both affected paths — set (`_set_thread_status`) and clear (the em","Any deployment with slack-sdk >=3.44.0 gets no indicator and no logged error."],"workaround":null,"fixed_in":null,"score":120.1,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#1855","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":1855,"title":"feat(terminal): Multi-backend terminal — local + N named remotes with persistent shell","url":"https://github.com/NousResearch/hermes-agent/issues/1855","state":"open","state_reason":null,"labels":["type/feature","backend/ssh","comp/tools","tool/terminal","P3","needs-decision"],"created":"2026-03-18T01:26:28Z","updated":"2026-09-23T18:55:08Z","closed":null,"reactions":17,"thumbs_up":17,"comments":11,"severity":"medium","severity_reasons":["engagement 28","class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","network"],"cosmetic_ui":false,"summary":"Today, Hermes Agent supports exactly one terminal backend at a time — set globally via terminal.backend in config.yaml (mapped to TERMINALENV). You pick local, ssh, docker, modal, daytona, or singularity, and every terminal() call routes…","versions":[],"error_snippets":["timeout: 180","\"description\": \"Execution target: 'local' (default) or a named backend (e.g. 'macbook'). Omit for default.\"","doesn't persist. Environment variables don't survive. Shell state is gone between calls. The agent ends up prepending","terminal_tool.py:463","terminal_tool.py:539"],"workaround":null,"fixed_in":null,"score":119.1,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#142461","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":142461,"title":"Automation wakes into auto-created Discord threads are refused admission_conflict forever (parents never resume after children finish)","url":"https://github.com/NousResearch/hermes-agent/issues/142461","state":"open","state_reason":null,"labels":["type/bug","comp/gateway","tool/delegate","platform/discord","P3","area/sessions"],"created":"2026-10-21T08:54:10Z","updated":"2026-10-25T13:36:04Z","closed":null,"reactions":6,"thumbs_up":6,"comments":8,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"With discord.autothread: true, every automation wake that targets a session whose thread was auto-created is refused at admission: The drain requeues the event and retries forever, so parent agents never resume after their children finish…","versions":["0.22.2-era"],"error_snippets":["restored.source (latest in-thread envelope): {platform, chat_id, chat_type, thread_id, user_id, ...}","event.source (origin-rebuilt): {... same 12 keys ..., auto_thread_created: True, auto_thread_initial_name: '...'}","With `discord.auto_thread: true`, every automation wake that targets a session whose thread was **auto-created** is refused at admission:","The drain requeues the event and retries forever, so **parent agents never resume after their children finish**: `delegate_task` children complete (results verifiable in their transcripts), background-process watches fir","Reproduced deterministically on a live gateway (v0.22.2-era checkout, single profile, single Discord adapter): refusals from the first attempt, across gateway restarts and code updates, on every auto-created-thread sessi"],"workaround":null,"fixed_in":null,"score":118.4,"first_seen":"2026-10-23T09:23:24Z"},{"id":"NousResearch/hermes-agent#141862","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":141862,"title":"Plugin tools can't declare execution_timeout — register_tool() drops it, so every plugin tool is capped at the 420s deadline","url":"https://github.com/NousResearch/hermes-agent/issues/141862","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/plugins","P2"],"created":"2026-10-20T04:04:01Z","updated":"2026-10-20T05:42:41Z","closed":null,"reactions":4,"thumbs_up":2,"comments":7,"severity":"medium","severity_reasons":["class:mcp/tools","class:network"],"topic":"mcp/tools","classes":["mcp/tools","network"],"cosmetic_ui":false,"summary":"Plugin tools can't raise their own execution deadline. PluginContext.registertool() (hermescli/plugins.py) does not accept or forward executiontimeout, but tools.registry.register() supports it and…","versions":[],"error_snippets":["execution_timeout","agent.tool_dispatch_helpers._extend_tool_timeout()","_DEFAULT_CONCURRENT_TOOL_TIMEOUT_S","timeouts.tools.sequential_call","subprocess.run(..., timeout=900)"],"workaround":{"text":"`timeouts.tools.sequential_call: 960` in `config.yaml`. This raises the ceiling for every tool, so a wedged tool now blocks for up to 16 minutes instead of 7. It also leaves the concurrent-batch path at 420 s.","source":"issue body","url":"https://github.com/NousResearch/hermes-agent/issues/141862"},"fixed_in":null,"score":103.0,"first_seen":"2026-10-20T09:28:14Z"},{"id":"NousResearch/hermes-agent#135217","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":135217,"title":"[Bug]: v0.21.6 shows the v0.21.5 release date (2026.9.24) in `hermes --version` and the banner","url":"https://github.com/NousResearch/hermes-agent/issues/135217","state":"open","state_reason":null,"labels":["type/bug","comp/cli","P2","area/install-update"],"created":"2026-10-08T17:01:19Z","updated":"2026-10-25T16:56:48Z","closed":null,"reactions":2,"thumbs_up":2,"comments":9,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","self-host/headless"],"cosmetic_ui":false,"summary":"On v0.21.6 the version line still carries the release date of v0.21.5: The version is right (it comes from the install stamp), but the date in parentheses is hermescli.releasedate, which is still \"2026.9.24\" in the v0.21.6 tag and on main…","versions":["0.21.6","0.21.5","2026.9.24","2026.10.8"],"error_snippets":["elevenlabs not set","--- errors.log (last 100 lines) ---","(file empty)","(file not found)","(not on this host: written by Hermes Desktop on the machine running the app, not by this backend. If the desktop connects to a remote/docker/SSH backend, collect it on that client machine — expected at /opt/data/logs/des"],"workaround":null,"fixed_in":null,"score":95.4,"first_seen":"2026-10-26T10:12:02Z"},{"id":"NousResearch/hermes-agent#32903","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":32903,"title":"openai-codex provider crashes: SDK parse_response fails on null output from Codex backend","url":"https://github.com/NousResearch/hermes-agent/issues/32903","state":"closed","state_reason":"completed","labels":["type/bug","comp/agent","provider/openai","P3"],"created":"2026-05-27T00:49:26Z","updated":"2026-10-17T13:06:19Z","closed":"2026-05-27T03:06:26Z","reactions":25,"thumbs_up":25,"comments":17,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","install/update","auth/session"],"cosmetic_ui":false,"summary":"Hermes v0.14.0 (latest, updated 2026-05-27 with 471 commits pulled) crashes on every hermes chat call when using openai-codex provider with gpt-5.5. The ChatGPT Codex backend (chatgpt.com/backend-api/codex) returns output: null in…","versions":["0.14.0","2.38.0","2026.5.16","2.24.0"],"error_snippets":["Error: 'NoneType' object is not iterable","output: null","Hermes v0.14.0 (latest, updated 2026-05-27 with 471 commits pulled) crashes on every `hermes chat` call when using `openai-codex` provider with `gpt-5.5`.","The ChatGPT Codex backend (`chatgpt.com/backend-api/codex`) returns `output: null` in `response.completed` SSE stream events. The OpenAI Python SDK's `parse_response()` at `openai/lib/_parsing/_responses.py:61` does `for"],"workaround":null,"fixed_in":null,"score":93.2,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#132817","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":132817,"title":"Pain cluster: one transient 429 / entitlement cooldown benches a credential for days — no reset-time probe, no visibility, no pointer to `hermes auth reset` (13 reports this week)","url":"https://github.com/NousResearch/hermes-agent/issues/132817","state":"open","state_reason":null,"labels":["type/bug","comp/agent","comp/cli","provider/openai","area/auth","P2","sweeper:risk-security-boundary","area/profiles","from-pain-miner"],"created":"2026-10-04T16:11:23Z","updated":"2026-10-20T07:46:01Z","closed":null,"reactions":2,"thumbs_up":2,"comments":8,"severity":"critical","severity_reasons":["title:data-loss/security"],"topic":"auth/session","classes":["auth/session","network","always-on/daemon","crash/hang"],"cosmetic_ui":false,"summary":"A single transient 429 / modelentitlement cooldown on one credential benches that credential (and often the whole provider row, or every auxiliary call) for hours to days, with no reset-time probe, no visible \"in cooldown until T because…","versions":[],"error_snippets":["s, or a fallback model that never lets go, and then hand-edit","HTTP 429: The usage limit has been reached","last_error_*","/ reset headers everywhere (pool, aux, kanban); at","This is a pain-miner umbrella: the individual mechanisms are filed below. What is not filed is that this is **one class** (cooldown persistence + scope + visibility + reset), that `hermes auth reset ` already exists (cre"],"workaround":null,"fixed_in":null,"score":91.6,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#125437","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":125437,"title":"Pain cluster: a failed update leaves a half-applied install with a raw error and no in-product recovery — 5 mechanisms, 15 Discord threads this week, every fix is a hand-typed recipe","url":"https://github.com/NousResearch/hermes-agent/issues/125437","state":"open","state_reason":null,"labels":["type/bug","comp/cli","P1","sweeper:risk-compatibility","comp/desktop","area/install-update","from-pain-miner","os/windows"],"created":"2026-09-27T16:09:32Z","updated":"2026-10-25T16:10:12Z","closed":null,"reactions":1,"thumbs_up":1,"comments":16,"severity":"high","severity_reasons":["label:p1"],"topic":"install/update","classes":["install/update","always-on/daemon"],"cosmetic_ui":false,"summary":"When hermes update / the Desktop updater fails, the install is left half-applied (Desktop launches then closes, gateway venv missing pydanticcore, git checkout carrying partial-clone config) and the product prints the raw underlying error…","versions":[],"error_snippets":["✗ Failed to fetch updates from origin. BUG: builtin/pack-objects.c:4842: should_include_obj …","tar.exe: Error opening archive: Can't initialize filter; unable to run program \"bzip2 -d\"","[X] failed to extract pinned git archive","index-pack failed","This is a pain-miner umbrella: the individual mechanisms are already filed (linked below). What is not filed is that the *class* has no in-product self-recovery and that the fixes for every mechanism are sitting in open "],"workaround":null,"fixed_in":null,"score":91.3,"first_seen":"2026-10-26T10:12:02Z"},{"id":"NousResearch/hermes-agent#136567","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":136567,"title":"Telegram DM topics: opening message of a newly created topic is delivered thread-less → lobby recovery misroutes it to the previous topic","url":"https://github.com/NousResearch/hermes-agent/issues/136567","state":"closed","state_reason":"completed","labels":["type/bug","comp/gateway","platform/telegram","P2","sweeper:risk-session-state","sweeper:risk-message-delivery","area/sessions","cause/upstream"],"created":"2026-10-11T11:11:59Z","updated":"2026-10-20T04:48:46Z","closed":"2026-10-20T04:47:55Z","reactions":8,"thumbs_up":8,"comments":32,"severity":"medium","severity_reasons":["engagement 40","class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","network"],"cosmetic_ui":false,"summary":"In a forum-enabled bot DM (Telegram \"Threads\" feature), when the user creates a new topic via the client's \"New thread\" composer, Telegram now delivers the opening message without messagethreadid (thread-less), while the forumtopiccreated…","versions":["0.21.6+607.gc573316"],"error_snippets":["event.source.thread_id","In a forum-enabled bot DM (Telegram \"Threads\" feature), when the user creates a new topic via the client's \"New thread\" composer, Telegram now delivers the **opening message without `message_thread_id`** (thread-less), w","Hermes' lobby recovery (`_recover_telegram_topic_thread_id`, `gateway/run_topics.py`) then pins the thread-less message to the user's **most-recent bound topic**: the message is processed in the *previous* session (inter","User-visible symptom: \"when I write from 'New thread' it keeps answering in the last active thread and creates an empty section.\"","A local user plugin implements exactly this (narrow PTB `filters.MessageFilter` for `forum_topic_created` via `register_platform_handler`, plus a `pre_gateway_dispatch` hook that rewrites `event.source.thread_id`); verif"],"workaround":null,"fixed_in":null,"score":89.7,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#72298","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":72298,"title":"[Bug]: Hermes shows passwords in Telegram chat","url":"https://github.com/NousResearch/hermes-agent/issues/72298","state":"open","state_reason":null,"labels":["type/bug","comp/agent","comp/gateway","tool/browser","platform/telegram","P2","needs-repro","sweeper:risk-message-delivery","sweeper:risk-security-boundary"],"created":"2026-07-26T23:29:05Z","updated":"2026-09-17T13:27:22Z","closed":null,"reactions":11,"thumbs_up":8,"comments":5,"severity":"medium","severity_reasons":["engagement 16","class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","auth/session"],"cosmetic_ui":false,"summary":"Hi! I'm developing a skill that uses the following stack: Kimi K3; from OpenCode Go Bitwarden; for secrets (using the \"official\" resource from Hermes docs) Browserbase headless; integrated in Hermes (free) without API key - as is. Hermes…","versions":["0.19.0","2026.7.20","3.10.12"],"error_snippets":[],"workaround":null,"fixed_in":null,"score":88.8,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#138649","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":138649,"title":"[Bug]: Telegram init hangs pre-socket inside gateway (no SYN, healthy loop, standalone 0.3s) — recurring #63309-family variant","url":"https://github.com/NousResearch/hermes-agent/issues/138649","state":"open","state_reason":null,"labels":["type/bug","comp/gateway","comp/plugins","platform/telegram","P1","sweeper:risk-message-delivery"],"created":"2026-10-14T22:05:44Z","updated":"2026-10-15T11:48:36Z","closed":null,"reactions":1,"thumbs_up":0,"comments":5,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang","mcp/tools","network","install/update","auth/session"],"cosmetic_ui":false,"summary":"Telegram init hangs pre-socket inside the gateway process after a routine network blip, while the identical stack (same venv, same token, same transports, same SSL context) connects in 0.3s standalone. Appears to be a new variant of the…","versions":[],"error_snippets":["ConnectError('')","TimeoutError","executor threads idle in","primitive bound to a different (earlier) loop/event-loop context — the classic \"works standalone, hangs in gateway\" signature: no fd, no timer, loop idle in","tasks after the first fatal error ("],"workaround":null,"fixed_in":null,"score":88.3,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#131055","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":131055,"title":"Linux Desktop: second-instance launches poison the sandbox fallback marker → sticky --no-sandbox → renderer SIGILL loop (/dev/shm ESRCH)","url":"https://github.com/NousResearch/hermes-agent/issues/131055","state":"open","state_reason":null,"labels":["type/bug","P2","sweeper:risk-security-boundary","comp/desktop","desktop/shell"],"created":"2026-10-02T00:55:55Z","updated":"2026-10-24T20:23:39Z","closed":null,"reactions":1,"thumbs_up":1,"comments":23,"severity":"medium","severity_reasons":["engagement 24"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"On Linux, launching Hermes Desktop again while it is already running (the launcher, gtk-launch, or a hermes:// deeplink that starts the binary) can leave windows-sandbox-fallback.json stuck at {\"state\":\"fallback\",\"reason\":\"boot-loop\"}…","versions":[],"error_snippets":["ERROR:base/memory/platform_shared_memory_region_posix.cc:214] Creating shared memory in /dev/shm/.org.chromium.Chromium.XXXXXX failed: No such process (3)","ERROR:base/memory/platform_shared_memory_region_posix.cc:217] Unable to access(W_OK|X_OK) /dev/shm: No such process (3)","FATAL:base/memory/platform_shared_memory_region_posix.cc:219] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.","[deeplink] delivery failed: Object has been destroyed","[hermes] sandbox fallback enabled (sticky-fallback); launching with --no-sandbox (#38216, #121954)"],"workaround":null,"fixed_in":null,"score":85.4,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#143657","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":143657,"title":"[Bug]: macOS headless: gateway ensure aborts with service_manager_unavailable because launchctl print gui/<uid> returns 125","url":"https://github.com/NousResearch/hermes-agent/issues/143657","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/gateway","P2","os/macos"],"created":"2026-10-23T16:54:31Z","updated":"2026-10-24T09:41:00Z","closed":null,"reactions":1,"thumbs_up":1,"comments":2,"severity":"medium","severity_reasons":["class:always-on/daemon","class:self-host/headless"],"topic":"always-on/daemon","classes":["always-on/daemon","self-host/headless","install/update"],"cosmetic_ui":false,"summary":"What happens: hermes -z \"…\" (and any entrypoint that ensures the gateway) fails with Error: Gateway inaccessible: servicemanagerunavailable when run without a GUI login session — e.g. from a system LaunchDaemon with UserName= , or via sudo…","versions":["0.22.3","0.22.5","0.22.2"],"error_snippets":["Error: Gateway inaccessible: service_manager_unavailable",", if the LaunchAgent plist does not exist, either skip the"],"workaround":null,"fixed_in":null,"score":82.1,"first_seen":"2026-10-25T09:11:37Z"},{"id":"NousResearch/hermes-agent#118753","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":118753,"title":"Curator's automatic inactivity archival can silently break kanban swarm verifier/synthesizer (requesting-code-review, humanizer)","url":"https://github.com/NousResearch/hermes-agent/issues/118753","state":"open","state_reason":null,"labels":["type/bug","comp/agent","comp/cli","comp/cron","tool/skills","P2","needs-decision","area/profiles"],"created":"2026-09-22T03:46:14Z","updated":"2026-10-22T17:07:30Z","closed":null,"reactions":1,"thumbs_up":1,"comments":8,"severity":"medium","severity_reasons":["class:always-on/daemon","class:mcp/tools"],"topic":"always-on/daemon","classes":["always-on/daemon","mcp/tools","install/update","crash/hang"],"cosmetic_ui":false,"summary":"hermes kanban swarm's verifier role hardcodes the skill requesting-code-review (hermescli/kanbanswarm.py:238). This skill ships bundled (skills/software-development/requesting-code-review/), so it normally exists — but the Curator's…","versions":[],"error_snippets":["Error: Unknown skill(s): requesting-code-review","kanban.failure_limit",", and nothing prevents the exact same archival from recurring in another","Once archived, every subsequent `kanban swarm` verifier card crashes at launch with `Unknown skill(s): requesting-code-review`, hits `kanban.failure_limit` (default 2), and auto-blocks — with no board-visible explanation","`hermes curator pin` also cannot be used as a manual workaround for this specific skill: it explicitly refuses bundled/hub skills (*\"'requesting-code-review' is bundled or hub-installed — cannot pin (only agent-created s"],"workaround":null,"fixed_in":null,"score":81.6,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#122222","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122222,"title":"[Bug]: cron external worker cannot import dependencies on self-managed installs — every scheduled job fails before its ownership ack","url":"https://github.com/NousResearch/hermes-agent/issues/122222","state":"closed","state_reason":"completed","labels":["type/bug","comp/cron","P1","sweeper:risk-compatibility","area/install-update"],"created":"2026-09-25T03:38:39Z","updated":"2026-10-13T15:07:08Z","closed":"2026-09-28T22:02:39Z","reactions":4,"thumbs_up":3,"comments":34,"severity":"high","severity_reasons":["label:p1"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"On a self-managed (shell-installer / PM) Hermes install, every scheduled cron job fails before it can run. The restart-safe external worker is spawned as sys.executable -m cron.scheduler with a sanitized environment whose PYTHONPATH…","versions":[],"error_snippets":["Restart-safe cron worker dispatch failed: cron external worker exited before","ownership acknowledgement (exit 1); worker stderr:","ModuleNotFoundError: No module named 'ruamel'","STORE=\"$(hermes gateway status --json 2>/dev/null | python3 -c 'import json,sys;print(json.load(sys.stdin)[\"python\"])' 2>/dev/null)\" \\","|| STORE=\"$HERMES_HOME/tools/python-\"*/bin/python3 # any launcher Python; the point is it exposes no deps"],"workaround":null,"fixed_in":null,"score":80.3,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#122183","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122183,"title":"[Bug]: Windows gateway on the PM runtime prepends the pre-PM venv and crashes hosted_room_worker (No module named 'pydantic_core._pydantic_core')","url":"https://github.com/NousResearch/hermes-agent/issues/122183","state":"closed","state_reason":"completed","labels":["type/bug","comp/gateway","P1","sweeper:risk-message-delivery","sweeper:risk-compatibility","sweeper:risk-platform-windows","area/install-update","os/windows"],"created":"2026-09-25T03:09:14Z","updated":"2026-10-17T10:21:03Z","closed":"2026-09-26T14:27:58Z","reactions":2,"thumbs_up":2,"comments":24,"severity":"high","severity_reasons":["label:p1","title:breakage"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","crash/hang"],"cosmetic_ui":false,"summary":"A Windows install that moved to the PM runtime (managed Python 3.14, dependencies under installs/ /environments/ /venv) still has the old pre-PM \\venv (Python 3.11) on disk. After hermes update --gateway respawned the messaging gateway…","versions":["10.0.26200","3.14.7"],"error_snippets":["ERROR gateway.run: Supervised task hosted_room_worker died: ModuleNotFoundError(\"No module named 'pydantic_core._pydantic_core'\")","ERROR gateway.run: Supervised task hosted_room_worker died 5 times in rapid succession (each within 300s of restart) — giving up restarts","File \"<install>\\gateway\\run_startup.py\", line 794, in _start_hosted_room_worker_sync","ModuleNotFoundError: No module named 'pydantic_core._pydantic_core'","PYTHONPATH=<install>;<install>\\venv\\Lib\\site-packages;<install>;<HERMES_HOME>\\installs\\<id>\\environments\\<gen>\\venv\\Lib\\site-packages"],"workaround":null,"fixed_in":null,"score":79.7,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#122349","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122349,"title":"Plugin runtime state inside a member folder causes an infinite sync/rebuild/re-exec loop","url":"https://github.com/NousResearch/hermes-agent/issues/122349","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/plugins","P3","sweeper:risk-compatibility","area/install-update"],"created":"2026-09-25T05:52:16Z","updated":"2026-10-06T02:32:24Z","closed":null,"reactions":1,"thumbs_up":1,"comments":9,"severity":"medium","severity_reasons":["class:install/update","class:mcp/tools"],"topic":"install/update","classes":["install/update","mcp/tools","always-on/daemon","crash/hang"],"cosmetic_ui":false,"summary":"pm/workspace.py::membersstamp() hashes every file in each enabled plugin member directory to decide whether the recorded dependency environment is current (pm/install.py::venviscurrent). The only exclusions are the hard-coded MEMBEREXCLUDE…","versions":[],"error_snippets":[") and names ending in","~/.hermes/installs/<id>/environments/","`pm/workspace.py::members_stamp()` hashes every file in each enabled plugin","member directory to decide whether the recorded dependency environment is","current (`pm/install.py::venv_is_current`). The only exclusions are the"],"workaround":null,"fixed_in":null,"score":77.2,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#122402","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122402,"title":"[Bug]: Ubuntu historical takeover fails building python-olm when managed Python requires missing clang++","url":"https://github.com/NousResearch/hermes-agent/issues/122402","state":"open","state_reason":null,"labels":["type/bug","comp/cli","platform/matrix","P2","sweeper:risk-compatibility","area/install-update"],"created":"2026-09-25T06:52:13Z","updated":"2026-10-23T15:11:57Z","closed":null,"reactions":1,"thumbs_up":1,"comments":14,"severity":"medium","severity_reasons":["engagement 15","class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"A git-installed Hermes update on Ubuntu 24.04 failed while preparing the new isolated dependency environment during the historical PM takeover. The selected features included matrix; mautrix[encryption] pulled python-olm==3.2.16, which…","versions":["3.2.16","0.21.4","0.20.5","0.0.0"],"error_snippets":["✗ Installing Python dependencies failed","building '_libolm' extension","error: [Errno 2] No such file or directory: 'clang++'","hint: `python-olm` (v3.2.16) was included because `hermes-agent[matrix]` (v0.0.0) depends on `mautrix[encryption]` (v0.21.1) which depends on `python-olm`","Update preparation failed: venv: uv sync exited 1"],"workaround":null,"fixed_in":null,"score":76.1,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#142336","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":142336,"title":"[Bug]: Desktop: reasoning-effort pill spins forever when opening a messaging-platform session","url":"https://github.com/NousResearch/hermes-agent/issues/142336","state":"open","state_reason":null,"labels":["type/bug","comp/gateway","platform/wecom","P2","area/sessions"],"created":"2026-10-21T02:43:15Z","updated":"2026-10-25T03:31:41Z","closed":null,"reactions":1,"thumbs_up":1,"comments":3,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon"],"cosmetic_ui":false,"summary":"Opening a conversation that belongs to a messaging platform (Telegram DM/group, WeChat, Feishu, …) in Hermes Desktop leaves the composer's reasoning-effort pill in its loading state indefinitely. It never paints the chat's actual level…","versions":["0.22.2+2953.g0b8dee0"],"error_snippets":["but no effort column, and the desktop tile path reads","Opening a conversation that belongs to a messaging platform (Telegram DM/group, WeChat, Feishu, …) in Hermes Desktop leaves the composer's reasoning-effort pill in its loading state indefinitely. It never paints the chat","3. The composer's model pill paints (from the composer's own sticky state), the effort pill shows the pending spinner and never resolves.","4. Pick any effort level once — the pill paints and the pick persists per chat across gateway restarts.","1. Desktop marks a resumed slice's effort pending by design (`markReasoningEffortPending`, `apps/desktop/src/lib/chat-runtime.ts`): the resume reply carries no `reasoning_effort` (since #79807), and the clearing value ar"],"workaround":null,"fixed_in":null,"score":74.0,"first_seen":"2026-10-25T09:11:37Z"},{"id":"NousResearch/hermes-agent#138329","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":138329,"title":"httpx2==2.12.0's 1 MiB per-SSE-event cap silently breaks MCP servers with a large tools/list (reported as \"SSE stream ended without a response\")","url":"https://github.com/NousResearch/hermes-agent/issues/138329","state":"closed","state_reason":"completed","labels":["type/bug","comp/tools","tool/mcp","P2","area/streaming","cause/upstream"],"created":"2026-10-14T10:26:07Z","updated":"2026-10-24T00:40:35Z","closed":"2026-10-24T00:40:35Z","reactions":3,"thumbs_up":3,"comments":5,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","network","install/update"],"cosmetic_ui":false,"summary":"After upgrading to an environment that has httpx2==2.12.0 (the pin Hermes carries for the mcp extra since bc8545bd1a, \"bump httpx2/httpcore2 2.7.0 -> 2.12.0 for the audit advisories\"), any HTTP MCP server whose tools/list response arrives…","versions":["2.12.0","2.7.0","2.9.1","2.12"],"error_snippets":["✗ Connection failed (12.3s): SSE stream ended without a response","httpx2.SSEError: Server-sent event exceeded the 1048576 byte limit.","raise SSEError(f\"Server-sent event exceeded the {self._max_event_size} byte limit.\")","MCP server '<x>' failed initial connection after 3 attempts, parking until a reconnect is requested","EventSource.__init__"],"workaround":null,"fixed_in":null,"score":69.8,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#142491","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":142491,"title":"Gateway group workspace UX gaps: no paste/drag, no @-autocomplete, no inline image rendering, members can't send files","url":"https://github.com/NousResearch/hermes-agent/issues/142491","state":"open","state_reason":null,"labels":["type/feature","P3","comp/desktop","desktop/chat","desktop/files"],"created":"2026-10-21T10:30:54Z","updated":"2026-10-21T10:36:27Z","closed":null,"reactions":2,"thumbs_up":2,"comments":0,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang"],"cosmetic_ui":false,"summary":"The gateway-owned group chat workspace (canonical-group, Desktop v0.22.2) lost several capabilities the legacy Desktop room UI had. Five gaps, all in the same surface: Composer: no clipboard image paste, no drag-and-drop — a bare in…","versions":["0.22.2"],"error_snippets":["extractClipboardImageBlobs","The gateway-owned group chat workspace (canonical-group, Desktop v0.22.2) lost several capabilities the legacy Desktop room UI had. Five gaps, all in the same surface:","3. **Sparse timeline** — message grouping, author styling/avatars, timestamps and thread affordances from the legacy `group-chat-view.tsx` are gone; the room reads like a debug workspace rather than a chat.","4. **Attachments are not rendered inline** — `canonical-group-history.tsx` shows image attachments as filename chips with a download action only; there is no ` ` preview, so \"look at this screenshot\" requires download + ","5. **Members cannot send images/files** — member replies are text-only in the room protocol, and `::preview{file=...}` directives (which render in normal chats) show as raw text in groups. Any artifact a member produces "],"workaround":null,"fixed_in":null,"score":67.5,"first_seen":"2026-10-23T09:23:24Z"},{"id":"NousResearch/hermes-agent#124471","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":124471,"title":"Hindsight core→plugin migration traps source install in interrupted update / dependency prompt loop","url":"https://github.com/NousResearch/hermes-agent/issues/124471","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/plugins","tool/memory","P3","sweeper:risk-compatibility","area/install-update","Plugin Catalog"],"created":"2026-09-26T21:22:17Z","updated":"2026-10-17T08:11:44Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"medium","severity_reasons":["class:install/update","class:mcp/tools"],"topic":"install/update","classes":["install/update","mcp/tools","crash/hang"],"cosmetic_ui":false,"summary":"After updating a git/source installation to Hermes Agent v0.21.5+2959.ga342e65 (commit a342e6563d), the automatic migration of the Hindsight memory provider from core to the plugin catalog gets stuck while preparing the plugin's Python…","versions":["0.21.5+2959.ga342e65","0.10.1","2026.9.24","2.24.0"],"error_snippets":["- hindsight-embed>=0.10.1,<1","^CSkipped — run `hermes plugins enable` when ready to prepare them.","The installed plugin and active environment are unchanged..","File \".../hermes_bootstrap.py\", line 532, in <module>","return self._wait(timeout=timeout)"],"workaround":null,"fixed_in":null,"score":67.1,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#133992","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":133992,"title":"[Bug]: Regression of #78119 / #87514: macOS Desktop update hand-off refuses its own hermes update (custodian + second-resolution delegate ct)","url":"https://github.com/NousResearch/hermes-agent/issues/133992","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","P2","needs-repro","sweeper:risk-compatibility","comp/desktop","area/install-update"],"created":"2026-10-06T15:58:06Z","updated":"2026-10-10T17:44:38Z","closed":"2026-10-10T17:44:38Z","reactions":4,"thumbs_up":3,"comments":24,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","always-on/daemon"],"cosmetic_ui":false,"summary":"On macOS, every update started from the Desktop app's Update button fails with exit code 2 because hermes update refuses the lock held by its own hand-off: The PID named in the error is the custodian that scripts/desktop-update/posix.sh…","versions":["0.005","3.14.7","0.21.5+8102.g0dbaf33","0.21.5+8002.g781334e"],"error_snippets":["The relevant excerpts are below. I'm happy to share more specific output on request.","19:51:52 hermes update exit code: 2","# Earlier run on 781334eea4: the hand-off recorded the delegate's ct as 1791301233.000.","ct:1791301233.508","detached update FAILED (exit 2)"],"workaround":{"text":"quit the Desktop app and run `~/.hermes/hermes-agent/.hermes/bin/hermes update` in a terminal.","source":"issue body","url":"https://github.com/NousResearch/hermes-agent/issues/133992"},"fixed_in":null,"score":66.2,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#135910","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":135910,"title":"pm repair cannot commit a dependency environment on a case-insensitive filesystem: shutil.copytree dies with Errno 17 on the bundled CPython terminfo","url":"https://github.com/NousResearch/hermes-agent/issues/135910","state":"open","state_reason":null,"labels":["type/bug","comp/cli","tool/file","P2","sweeper:risk-compatibility","area/install-update","os/macos"],"created":"2026-10-10T01:27:34Z","updated":"2026-10-19T23:31:42Z","closed":null,"reactions":2,"thumbs_up":2,"comments":3,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"On the official Docker image (linux-arm64, v0.21.6) with HERMESHOME on a case-insensitive volume (macOS/APFS default — a plain Docker Desktop bind mount under /Users/...), no dependency environment can ever be committed for the install…","versions":["0.21.6"],"error_snippets":["hermes: no dependency environment is committed for this install; run `hermes pm repair`","hermes: dependency repair failed: [('.../tools/python-3.14.7+.../share/terminfo/e',","'.../installs/<key>/environments/<id>/workspace/tools/python-3.14.7+.../share/terminfo/e',","\"[Errno 17] File exists: '.../terminfo/e'\"), ...]; run `hermes pm repair`","for entry in source.iterdir():"],"workaround":null,"fixed_in":null,"score":66.2,"first_seen":"2026-10-20T09:28:14Z"},{"id":"NousResearch/hermes-agent#135344","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":135344,"title":"kanban dispatcher: _pid_recycled compares the composed worker fingerprint by exact equality, so live macOS workers read as recycled and get duplicated","url":"https://github.com/NousResearch/hermes-agent/issues/135344","state":"open","state_reason":null,"labels":["type/bug","comp/cli","comp/cron","P2","sweeper:risk-automation","os/macos"],"created":"2026-10-08T22:48:59Z","updated":"2026-10-20T00:51:37Z","closed":null,"reactions":1,"thumbs_up":1,"comments":6,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang"],"cosmetic_ui":false,"summary":"hermescli/kanbandbdispatch.py::pidrecycled has a string branch for the composed worker fingerprint (\" | \") that compares the recorded value to a freshly computed one with EXACT equality. On hosts without /proc (macOS) the start-time half…","versions":[],"error_snippets":["real = _process_fingerprint(pid) # \"|179149919058\" on macOS: empty epoch, start time","except (TypeError, ValueError):","\"<instantiation-epoch>|<start-time>\"","`gateway/status.py` already documents this and already tolerates it: the integer branch of the same function uses `start_time_fingerprints_match` with a 200cs tolerance, and its comment names the macOS `kern.boottime` ad","Keep the epoch half exact, because it is the reboot witness, and hand the start-time halves to the same tolerance comparator the integer branch already uses:"],"workaround":null,"fixed_in":null,"score":65.2,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#122299","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122299,"title":"kanban dispatcher: worker spawn argv guard checks importability in parent, unsound for bare-interpreter child (ModuleNotFoundError: hermes_cli)","url":"https://github.com/NousResearch/hermes-agent/issues/122299","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","comp/cron","P2","sweeper:risk-compatibility","area/install-update","area/profiles"],"created":"2026-09-25T04:50:46Z","updated":"2026-09-28T10:37:12Z","closed":"2026-09-28T10:37:12Z","reactions":5,"thumbs_up":5,"comments":13,"severity":"medium","severity_reasons":["engagement 18","class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","crash/hang"],"cosmetic_ui":false,"summary":"resolvehermesargv() in hermescli/kanbandbdispatch.py decides the kanban worker's spawn argv using an importability check evaluated in the gateway (parent) process, but that result does not hold for the freshly-spawned child. On installs…","versions":[],"error_snippets":["cd /tmp && ~/.hermes/tools/python-3.14.7+.../bin/python3 -m hermes_cli.main --version; echo exit=$?","# -> ModuleNotFoundError: No module named 'hermes_cli'; exit=1","cd /tmp && ~/.hermes/hermes-agent/.hermes/bin/hermes --version; echo exit=$?","sys.executable","package, every worker crashes on startup with"],"workaround":{"text":"Pin `HERMES_BIN` to the shim for the gateway via a systemd drop-in (survives self-update, unlike a source patch):","source":"issue body","url":"https://github.com/NousResearch/hermes-agent/issues/122299"},"fixed_in":null,"score":63.4,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#135500","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":135500,"title":"[Bug]: Intermittent server_error with openai-codex across models on Windows Desktop","url":"https://github.com/NousResearch/hermes-agent/issues/135500","state":"open","state_reason":null,"labels":["type/bug","comp/agent","platform/discord","provider/openai","P2","needs-repro","comp/desktop","os/windows"],"created":"2026-10-09T08:08:09Z","updated":"2026-10-17T07:47:32Z","closed":null,"reactions":2,"thumbs_up":2,"comments":3,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","always-on/daemon","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"Hermes Agent intermittently fails with APIError and servererror when using the openai-codex provider with gpt-6.1-sol. The issue occurs in both Hermes Desktop and Discord Gateway on Windows 11. Some requests complete successfully…","versions":[],"error_snippets":["Provider unavailable (server_error)","I can provide sanitized diagnostic output and relevant log excerpts upon request.","Relevant sanitized log excerpt:","status=error","error_retained=True"],"workaround":null,"fixed_in":null,"score":63.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"NousResearch/hermes-agent#135965","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":135965,"title":"[Bug]: Telegram DM topic mode: typing in All to start a new topic hijacks the actively running topic","url":"https://github.com/NousResearch/hermes-agent/issues/135965","state":"closed","state_reason":"completed","labels":["type/bug","comp/gateway","platform/telegram","P3","sweeper:risk-session-state","sweeper:risk-message-delivery"],"created":"2026-10-10T04:20:10Z","updated":"2026-10-20T04:48:48Z","closed":"2026-10-20T04:47:56Z","reactions":12,"thumbs_up":12,"comments":5,"severity":"medium","severity_reasons":["engagement 17","class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon"],"cosmetic_ui":false,"summary":"In Telegram DM topic mode, when a topic is actively running, typing a new message in the All lane to start a new topic: creates a new (empty, dead) topic, and the message text lands in the actively running topic/session instead — the new…","versions":[],"error_snippets":["1. creates a new (empty, dead) topic, and","2. the message text lands in the **actively running** topic/session instead — the new topic stays empty, and the running conversation receives a message it wasn't meant to have.","1. Enable Telegram DM topic mode (e.g. `/topic` in the DM) and have at least one running/active topic.","3. Telegram creates the empty topic; the message you typed appears in the **previously active** topic instead.","The message is delivered to the lobby (no `message_thread_id`, or General id `\"1\"`), and `_recover_telegram_topic_thread_id` pins **any** lobby-shaped message to the user's most-recently-bound topic — so the new topic st"],"workaround":null,"fixed_in":null,"score":63.0,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#112028","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":112028,"title":"Support multi-surface access to the same session (desktop + mobile dashboard)","url":"https://github.com/NousResearch/hermes-agent/issues/112028","state":"open","state_reason":null,"labels":["type/feature","comp/gateway","P2","needs-decision","sweeper:risk-session-state","area/sessions","comp/tui-gateway"],"created":"2026-09-15T15:34:47Z","updated":"2026-10-20T19:03:34Z","closed":null,"reactions":2,"thumbs_up":0,"comments":7,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","self-host/headless"],"cosmetic_ui":false,"summary":"Hermes Agent: v0.21.3 Server: macOS (Mac mini) Surfaces: Desktop app + mobile dashboard When a session is open on the Desktop app (surface=desktop), a second surface (mobile dashboard, surface=tui) cannot submit messages to that same…","versions":["0.21.3"],"error_snippets":[") cannot submit messages to that same session — the server rejects it with","When a session is open on the Desktop app (surface=`desktop`), a second surface (mobile dashboard, surface=`tui`) cannot submit messages to that same session — the server rejects it with `SESSION_NOT_OWNED` (\"Session … a","Root cause found during investigation: `track_liveness` in `tui_gateway/session_lifecycle.py` is enabled only for `surface == \"desktop\"`, so a Desktop-opened session holds its lease indefinitely; `active_sessions.try_acq","3. At minimum: auto-release the lease when the owner surface is idle/unfocused, and return a distinct error code clients can surface to the user."],"workaround":null,"fixed_in":null,"score":59.2,"first_seen":"2026-10-21T09:24:21Z"},{"id":"NousResearch/hermes-agent#122326","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":122326,"title":"tools.lazy_deps.install_specs shim starts a full update takeover from hermes serve/gateway; Hindsight plugin turns it into a Desktop rebuild loop","url":"https://github.com/NousResearch/hermes-agent/issues/122326","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","comp/tools","comp/plugins","tool/memory","P3","sweeper:risk-compatibility","area/install-update"],"created":"2026-09-25T05:20:16Z","updated":"2026-10-17T10:20:25Z","closed":"2026-10-06T13:12:39Z","reactions":2,"thumbs_up":2,"comments":10,"severity":"medium","severity_reasons":["class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","mcp/tools","self-host/headless"],"cosmetic_ui":false,"summary":"tools.lazydeps.installspecs is now a shim that calls hermescli.oldupdater.stopforrelaunch(). That function starts the full historical update takeover (updatetakeover.py → updatefinish.py), which syncs PM and rebuilds Node deps, the TUI…","versions":["1.0.1","0.10.1"],"error_snippets":["_ensure_local_runtime (hindsight\\embedded.py:133)","is_available (hindsight\\__init__.py:446)","{\"restart_update\": false, \"plan\": null, \"argv\": [\"...\\\\.hermes\\\\bin\\\\hermes\", \"serve\", \"--host\", \"127.0.0.1\", \"--port\", \"0\"], ...}","hindsight-embed","appears at 00:43, 00:44, 00:54, 00:56 and 01:08. Each timestamp matches the start of a Desktop rebuild in"],"workaround":{"text":"Setting `memory.provider: ''` stops the loop. After Desktop relaunched, agent init finished normally and no takeover started. Hindsight memory is unavailable while this setting is in place.","source":"issue body","url":"https://github.com/NousResearch/hermes-agent/issues/122326"},"fixed_in":null,"score":59.1,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#9153","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":9153,"title":"Docker image missing 'dashboard' command (web UI not available in latest image)","url":"https://github.com/NousResearch/hermes-agent/issues/9153","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","P2","area/install-update"],"created":"2026-04-13T17:19:01Z","updated":"2026-10-17T13:25:19Z","closed":"2026-05-07T13:16:25Z","reactions":11,"thumbs_up":11,"comments":0,"severity":"medium","severity_reasons":["class:self-host/headless","class:install/update"],"topic":"self-host/headless","classes":["self-host/headless","install/update"],"cosmetic_ui":false,"summary":"The nousresearch/hermes-agent:latest Docker image on Docker Hub does not include the dashboard (or web) subcommand, making it impossible to run the web UI in containerized environments like Coolify. The dashboard command should be…","versions":[],"error_snippets":["hermes: error: argument command: invalid choice: 'dashboard' (choose from chat, model, gateway, setup, ...)","command exists in the current","The `nousresearch/hermes-agent:latest` Docker image on Docker Hub does not include the `dashboard` (or `web`) subcommand, making it impossible to run the web UI in containerized environments like Coolify."],"workaround":null,"fixed_in":null,"score":58.6,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#134381","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":134381,"title":"[Bug]: Update failed","url":"https://github.com/NousResearch/hermes-agent/issues/134381","state":"open","state_reason":null,"labels":["type/bug","comp/cli","P2","needs-repro","sweeper:risk-compatibility","comp/desktop","area/install-update"],"created":"2026-10-07T06:43:34Z","updated":"2026-10-17T07:50:31Z","closed":null,"reactions":4,"thumbs_up":4,"comments":0,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"Hi i tried to update the hermes client on MacOS but it failed. Error message is only Update failed so no info there :). Hermes Agent v0.21.5+8076.g85db7c3 (2026.9.24) · upstream 85db7c3a Install directory…","versions":["0.21.5+8076.g85db7c3","2026.9.24","2.24.0"],"error_snippets":["Hi i tried to update the hermes client on MacOS but it failed. Error message is only Update failed so no info there :).","Run Hermes Desktop App and press update -> failure"],"workaround":null,"fixed_in":null,"score":57.8,"first_seen":"2026-10-18T04:32:26Z"},{"id":"NousResearch/hermes-agent#111942","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":111942,"title":"[Bug]: CLI crashes on startup with NameError: name 'file_signature' is not defined (cli_tui_mixin.py, regression from #111408)","url":"https://github.com/NousResearch/hermes-agent/issues/111942","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","area/config","P0"],"created":"2026-09-15T14:05:17Z","updated":"2026-09-16T11:21:20Z","closed":"2026-09-15T15:17:08Z","reactions":5,"thumbs_up":4,"comments":12,"severity":"critical","severity_reasons":["label:p0"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"After updating to the latest main (24fd22b94d, v0.21.3 / 2026.9.14), the interactive CLI crashes immediately on startup with: This is a regression from 182ec5c28d (#111408, \"widen the remaining config.yaml stat caches to filesignature\")…","versions":["0.21.3","2026.9.14","3.11.16"],"error_snippets":["NameError: name 'file_signature' is not defined","Traceback (most recent call last):","sys.exit(main())","self._config_sig: tuple | None = file_signature(_cfg_path.stat()) if _cfg_path.exists() else None","to an empty tempdir, so"],"workaround":null,"fixed_in":null,"score":57.7,"first_seen":"2026-10-18T04:29:32Z"},{"id":"NousResearch/hermes-agent#130277","harness":"hermes","harness_name":"Hermes Agent","repo":"NousResearch/hermes-agent","number":130277,"title":"[Bug]: Desktop can't connect to a remote gateway since #127201: loopback renderer origin fails /api/ws Origin check","url":"https://github.com/NousResearch/hermes-agent/issues/130277","state":"closed","state_reason":"completed","labels":["type/bug","comp/cli","comp/gateway","area/auth","P1","sweeper:risk-security-boundary","comp/desktop"],"created":"2026-10-01T10:15:31Z","updated":"2026-10-01T20:01:24Z","closed":"2026-10-01T20:01:24Z","reactions":2,"thumbs_up":1,"comments":6,"severity":"high","severity_reasons":["label:p1"],"topic":"always-on/daemon","classes":["always-on/daemon","self-host/headless","auth/session","install/update","network"],"cosmetic_ui":false,"summary":"Since #127201 (d428df2a65, \"fix(desktop): restore YouTube embeds in the packaged app\"), the packaged Desktop renderer is served from http://127.0.0.1:47891. Its WebSocket upgrades therefore carry Origin: http://127.0.0.1:47891. When…","versions":["3.11.16"],"error_snippets":["'null' -> None","[renderer error:main] Hermes couldn't start: Error: Could not connect to Hermes gateway (WebSocket error before open)","at Tt.connectFailure (http://127.0.0.1:47891/assets/i18n-rJpzlE2h.js:2:12713)","or the bound host is accepted. Every","Hermes couldn't start: Error: Could not connect to Hermes gateway (WebSocket error before open)"],"workaround":null,"fixed_in":null,"score":54.1,"first_seen":"2026-10-18T04:32:26Z"}]}