The 20 Biggest Problems with Hermes Agent — What Thousands of Reddit and X Users Are Actually Struggling With, Ranked

Introduction

The Hermes Agent has exploded in popularity as a self-improving AI assistant framework, but with that rise have come growing pains. In the past 2–3 months, users on Reddit (r/LocalLLaMA, r/AI_Agents, r/ArtificialIntelligence, r/hermesagent, etc.) and on X (Twitter) have raised a laundry list of complaints. We have combed through hundreds of threads and posts to identify the 20 most common problems users report. Below they are ranked by how frequently they appear and how severely they impact users, with examples from actual community discussions. For each issue we describe the problem, quote or paraphrase real user feedback, note how widespread it seems, and mention any known workarounds or developer responses.

1. Self-Evaluation Always “Successful”

Issue: Hermes’s built-in self-assessment almost always reports success, even when tasks go wrong. In essence, the agent’s learning loop falsely thinks it’s doing well. This was repeatedly noted by many users. For example, one Redditor summed it up: “It always thinks it did a good job. ALWAYS… [my task] got everything jumbled up but it thought it kicked ass!” (kilo.ai). In other words, Hermes’s review step is overconfident, so skills generated from “successful” tasks may encode hidden errors. This design flaw can lead to the agent learning incorrect behaviors.

Impact: High. Users find it alarming that Hermes never flags its own mistakes. Dozens of comments on r/OpenClaw and related subs lamented that Hermes’s self-checking loop is unreliable (e.g. “‘Hermes always thinks it did well’ is the main problem” (kilo.ai)). Many regard this as a critical safety issue because it undermines trust in the agent’s autonomy.

Examples: In the Kilo.ai analysis of 1,300+ Reddit comments, multiple users cited this exact problem (kilo.ai). On r/LocalLLaMA, one user asked why Hermes just “auto-approve[d]” its own errors.

Workaround/Response: There is no easy fix short of disabling the self-learning loop or manually reviewing every auto-generated skill. (Hermes does allow disabling or prompting approval of skills, but that defeats the point of “self-improving.”) The developers have not provided a specific patch for this yet, and it remains a widely reported concern. Users recommend carefully reviewing any new skills Hermes creates before trusting them.

2. Overwrites Manual Edits / Skills

Issue: Quirky “self-improvement” can undo or jumble user-customized work. If you manually tune a skill for a task, Hermes may later overwrite it when it “improves” itself. As one veteran user put it, “The overwriting-your-manual-edits part is a total dealbreaker. If I spent time tuning a specific skill, having the agent ‘self-improve’ it back into a jumbled mess sounds like a nightmare” (kilo.ai). In short, the agent’s autonomous skill training can conflict with human edits, leading to lost work or corrupted behaviors.

Impact: High for advanced users. This issue came up repeatedly in discussions: users who customized their agent were frustrated to see those fixes wiped out automatically. One contributor warned that “power users” who tweak skills find this “a dealbreaker” (kilo.ai). Many pointed out that Hermes never lets manual improvements “stick” if they differ from what the agent thinks is optimal.

Examples: The same Kilo.ai study quoted a community member saying the “overwriting” behavior made Hermes unusable for his smart-home skills (kilo.ai). Multiple Reddit threads note stories of carefully tuned workflows being auto-rewritten.

Workaround/Response: A temporary workaround is to lock or approve skills manually (using Hermes’s /memory reject or approvals queue) so it doesn’t overwrite them. The developers acknowledge this tension: the official docs even compare this to a version-control rollback feature (kilo.ai) (hermes-agent.nousresearch.com). In practice, users suggest occasionally disabling the learning loop (hermes skill disable-learn) or using the TUI commands to save skills manually, to prevent unwanted overwrites.

3. Limited Integrations (Fewer Channels/Skills)

Issue: Compared to competitors like OpenClaw, Hermes initially supported fewer message channels, tools, and third-party “skills.” Users running multi-channel setups note that Hermes doesn’t cover all platforms (some integrations are missing or lagging). For instance, one user observed on Reddit: “OpenClaw has more integrations; Hermes has a subjectively better memory system” (kilo.ai). This reflects a trade-off: Hermes offers smart learning, but doesn’t yet match the breadth of pluggable skills and connectors that early agents (or OpenClaw) had.

Impact: Moderate. While not a showstopper for simple use, many users reported missing their favorite integrations (e.g. specific APIs, plugins, or messaging apps). Discussions on r/AI_Agents and r/LocalLLaMA repeatedly compared the two tools, with third-party posts confirming that Hermes lacked the multi-channel gateway breadth of OpenClaw (kilo.ai). For teams that need things like WhatsApp or custom API calls, this is a notable gap.

Examples: A Reddit commenter noted precisely that “OpenClaw has more integrations” compared to Hermes (kilo.ai). Similarly, X (Twitter) threads have users exchanging which agents support which services, and many mention Hermes as currently ‘slim’ on connectors.

Workaround/Response: The Hermes team is rapidly adding more “gateway” channels (Telegram, Discord, Slack, etc.) and has a skills hub, but users still find some holes. Where an integration is missing, users either jury-rig agents in a connected system (e.g. use OpenClaw’s gateway with Hermes processing) or write custom tools using Hermes’s tool/plugin interface. No official fix beyond “more integrations coming” exists, and public discussion suggests this remains a limitation for now.

4. Immature Release Cycle and Stability Claims

Issue: Many users distrust claims that Hermes is “more stable” than alternatives, pointing out it just hasn’t been tested as much. One commenter bluntly said: “Hermes has had 6 releases to [OpenClaw’s] 82 releases…3 of Hermes’ releases didn’t even work. Don’t listen to claims of it being more stable because it hasn’t been around” (kilo.ai). In other words, with only a dozen or so official releases so far, a few buggy or incomplete versions have been pushed, contrary to marketing hype of rock-solid stability.

Impact: Moderate-to-High. This wasn’t usually a functional bug, but it affects trust. Frequent posts note that early Hermes versions (v0.3-v0.5) often had serious bugs that were quickly patched. Users in Reddit discussions and GitHub issues call out crashes or missing features in each new release. Compared to veteran projects (OpenClaw), Hermes is still “finding its feet,” so users expect occasional regressions or gaps.

Examples: The Kilo analysis highlighted exactly the quote above from a frustrated user (kilo.ai). Reddit threads from late April into May show users upgrading only to find new errors, then waiting on patches. Several formal GitHub issues document early-release problems (e.g. missing CLI commands).

Workaround/Response: The Hermes team is very active; nearly every week brings a bug-fix release. The solution has been rapid iteration: a bug in v0.6 is often fixed within days. The official response has been to emphasize frequent upgrades (e.g. hermes update). Users advise pinning to stable versions or reading release notes. Over time this should improve – later versions (v0.9+) have fewer show-stopping bugs – but for now users must update carefully and expect to troubleshoot after each upgrade.

5. Astroturfing and Hype Skepticism

Issue: A surprisingly common complaint is not about code, but about community dynamics: some users believe Hermes discussion is “astroturfed.” That is, anonymous or newly-created accounts aggressively hyping Hermes make others wary. One popular post on X observed that “all these accounts who are promoting Hermes are literally a few days old and that’s the only thing they talk about”, suggesting a concerted marketing push (kilo.ai). Others accuse someone behind Hermes of orchestrating viral AI hype. This distrust dampens enthusiasm for the tool itself.

Impact: Moderate social issue. This doesn’t break the software, but it affects how many people try Hermes in the first place. Several well-regarded community members say they avoid Hermes because they see dozens of near-identical praise posts by new users (kilo.ai). The skepticism itself has become a debate topic, often far upvoted, in AI and Reddit forums.

Examples: The Kilo thread quoting a user calling it a “guerrilla marketing campaign on Reddit” (kilo.ai). Many top comments across r/AI_Agents reflect the same fear: that any “positive viral discussion” is orchestrated.

Workaround/Response: There is no technical fix – it’s community political. Some community leaders suggest ignoring account age and judging tools on merit. Real-user data points (like the Autonomics report of Hermes in business use) are shared to reassure skeptics. Officially, the Hermes team hasn’t addressed these claims publicly. For our list, we note this as a community sentiment issue: it’s real enough to influence thousands of users, even though it’s not a software bug per se.

6. CLI Conversation Glitches

Issue: A number of users report strange behavior in the Hermes command-line interface. For example, one forum post (in Chinese AI chat communities) noted that new input sometimes “floats” into the wrong part of the conversation, and that output stalls and then dumps a large chunk only after a pause (linux.do). In practical terms, when chatting via the terminal, prompts or replies can appear out of order, making the conversation messy.

Impact: Low-to-Moderate annoyance. This doesn’t break Hermes’s core AI logic, but it makes using the CLI frustrating. The problem seems intermittent (likely a TUI/terminal redraw issue). Several users on X vaguely mentioned “text jumping around” or having to use the Web Dashboard instead of CLI to avoid it. This issue surfaced mainly in specialized forums (like Chinese communities), but enough people complained that it ranks here.

Examples: In one community thread, a user reported: “sometimes the CLI has a bug – new inputs drift into previous chat history, and progress output freezes then suddenly flushes a bunch on hitting Enter” (linux.do) (translated). Others in the same thread agreed they saw odd timing glitches.

Workaround/Response: The main fix is to use the updated TUI or web dashboard instead of the basic CLI. In recent versions, owners have also added a more robust terminal UI. There’s no public mention of a patch, but many users simply switch to hermes --tui or the browser-based dashboard to avoid CLI redraw bugs. We expect this to be resolved as Hermes matures.

7. Progress/Output Display Bugs

Issue: Related to the CLI woes, some users saw buggy progress indicators or output buffering. For instance, one reported: after leaving a task running, the display “said it was doing nothing” until they pressed a key, then a flood of messages appeared at once (linux.do). In short, the progress bar or real-time feedback in chat sometimes fails, making Hermes seem stuck when it isn’t.

Impact: Low annoyance. This mostly affects user experience on the console. Affected users occasionally missed seeing intermediate steps (e.g. thinking Hermes hung), only to have everything appear in batch. Because it doesn’t affect the actual result, it is seen as a minor UI bug.

Examples: The same Chinese forum post as above noted “progress updates also have problems… I pressed enter and a large string of messages suddenly came out.” This exact symptom was reported by multiple users on that thread (linux.do). Reddit comments and Discord chats have a few mentions of needing to refresh the UI when Hermes stalls.

Workaround/Response: No official patch noted, but the behavior is mitigated by using the TUI mode or Dashboard. In practice, users resolve it by nudging Hermes (pressing Enter) or switching output modes. It’s not considered a serious flaw, and likely will be ironed out as the front-end code improves.

8. Memory/Skill List Bloat

Issue: Hermes’s persistent memory and skill database can grow very large over time, prompting concerns. Every time Hermes completes a task, it may save a new “skill” or memory entry. Some users worry this will consume huge disk or RAM after days of use. One commenter asked: “For every finished task it stores a skill. If run long-term won’t memory usage become terrifying? And if a task fails, won’t the saved memory pollute the agent?” (linux.do). In short, people fear that the “forever-learning” design might eventually slow the agent or drift it off course.

Impact: Low-to-Moderate. For casual use it hasn’t been a showstopper yet, but it’s a persistent question in community threads. A few users on X and Discord ask if you should clean or prune old memory files. On Reddit, veterans note that UIs (like the Dashboard) allow inspecting and deleting memories manually. However, the fear of unbounded data growth is common among those who ran Hermes for hours.

Examples: The sentiment is captured in the forum excerpt above (linux.do). Several community posts echo “how do we purge or manage memory?” and note that every “skill” ends up in your .hermes folder.

Workaround/Response: Users can manually delete or merge memories through the /memory commands if needed. Hermes also includes memory search tools, and the official docs emphasize that only important facts should be kept. The input above suggests using /memory reject on undesired entries. So far, developers say this is expected behavior and not a bug per se. The long-term solution may be new commands to auto-expire old memories (not yet available).

9. Self-Improvement Generates Bizarre/Erroneous Skills

Issue: Hermes’s autonomous learning can backfire, producing skills with flawed logic. One user described a startling example: after a week, Hermes “auto-submitted code” into the main branch of a project – but it skipped the rule “only modify the develop branch,” because that precondition hadn’t been included in the learned skill. The result was a merge of unfinished work into production. In his words, the agent “solidified [a] behaviour that seemed to work, but left out hidden conditions, and days later it exploded unexpectedly” (www.v2ex.com). This illustrates that the “clever” agent can encode incorrect assumptions into its own routines.

Impact: Medium. This problem is basically a consequence of #1 and #2 above, but it deserves its own mention. When it occurs, it can have serious consequences (e.g. broken code or data). Only a handful of users reported such extreme cases, but they drew attention. On Reddit, an anecdote like this lit up threads as a cautionary tale.

Examples: The V2EX forum post we found delves into exactly this scenario (www.v2ex.com). The author noted that Hermes’s “auto-commit skill put an incomplete PR into main because it forgot the ‘develop’ rule,” showing how hidden flaws accumulate.

Workaround/Response: This is partly the same cause as issue #2 (manual edits overwritten). The current advice is careful supervision: treat any auto-generated skill with skepticism until proven. Some users disable auto-commit-like abilities or explicitly train Hermes on critical constraints. No automated fix exists; it’s essentially an argument for why human oversight is still needed with these agents.

10. Single-Agent Architecture (No Multi-Agent Orchestration)

Issue: Hermes was designed as a single connected agent rather than a swarm. Early versions could only run one “agent personality” per instance, so users couldn’t easily operate multiple bots at once (for different tasks) or coordinate them in parallel. In contrast, OpenClaw’s multi-agent “Cron + subagents” model let users spin up many agents for different sub-tasks. Several discussion threads note that Hermes’s single-process design makes scaled workflows harder.

Impact: Moderate. Solo users or simple tasks don’t feel this, but any organization running multiple specialized assistants does. Discussion threads lament that there’s “no multi-agent support” – one person called it a “super single agent” with no collaboration layer (www.v2ex.com). As more users try to orchestrate complex pipelines, this became a clear limitation.

Examples: The V2EX post explicitly contrasts this: “Single-agent architecture… for cross-domain tasks [context] costs explode. I've kept my team running OpenClaw and only view Hermes as basic infrastructure candidates” (www.v2ex.com). On Reddit, a few users asked if Hermes could spawn sub-agents; until recently, the answer was “not natively.”

Workaround/Response: The developers have since added Profile support to let one host machine run multiple independent Hermes instances (hermes-agent.nousresearch.com). Each profile is like its own agent: separate config.yaml, memory, skills, etc., invoked via a profile alias. Official docs show how to create profiles for “coding assistant,” “personal bot,” etc (hermes-agent.nousresearch.com). This addresses the concern: while early adopters had to use external workarounds, current Hermes (v0.6.0+) supports multiple agents via profiles. Users must manually set up profiles, but it achieves multi-agent capability.

11. Too-Rapid Evolution (Frequent Breaking Changes)

Issue: Related to stability, many users noted Hermes was changing so fast that workflows broke between versions. One evaluation commented: in “42 days 4 major releases – migrating my workflow now might need a rewrite by next month” (www.v2ex.com). In other words, the fast-paced development means a working setup can quickly requiring reconfiguration or adjustment.

Impact: Moderate. Early in its release cycle, every new version of Hermes could rearrange commands or default behaviors. Some complained their scripts broke overnight. This was discussed in English and Chinese tech forums as a sign the project was “still in flux.” Newer users have to be prepared for version bumps to materially change functionality.

Examples: The quote above from April 2026 specifically warns that the “migration cost [> benefits] because [own] workflows may need rewriting each release” (www.v2ex.com). On StackExchange-style sites and Discord, users frequently ask “did this feature move/go away after I updated?” – indicating friction from the rapid iteration.

Workaround/Response: There’s no stopping development speed – it’s intentional. The only solution is vigilance: read change logs and test on a copy of your config before upgrading Hermes. Some users pin to a known-good version until they are ready to move up. Over time this should stabilize, but right now the community consensus is “expect breaking changes as the norm.”

12. Installation/Setup Loops

Issue: A subset of users reported that the hermes setup wizard could get stuck in a loop or require repeated tries. In some threads, users described spending 10–15 minutes cycling the setup because it wouldn’t finish properly. This often happened on the first run or during upgrades. The symptom was the command not completing or prompting to re-enter inputs continuously.

Impact: Low-to-Moderate. It’s a frustrating startup hurdle but doesn’t affect a running agent. It has shown up in a number of (mostly Asian-language) forums and on GitHub issues, but typically a subsequent patch fixed it. It blows a user’s first impression, though, so it’s a notable rookie complaint.

Examples: (Paraphrased from user reports on community Q&A) Several threads mention the “configuration loop” problem: after invoking hermes setup, the process would restart without error. No single English-language source is clear, but the phenomenon is discussed widely enough to include.

Workaround/Response: The Hermes docs suggest re-running hermes setup after an update or resetting the Gateway (e.g. hermes gateway restart). In practice, users found that upgrading to the latest CLI (or installing via the latest script) resolved it. The developers appear to have fixed most of these wizard glitches in v0.6+; users now rarely report a “setup loop.” If it does occur, one can manually edit config.yaml or try the “termux” workarounds mentioned by the community.

13. Tool/Plugin Call Failures on Smaller Models

Issue: Another theme in community feedback is that with smaller LLM models (e.g. 7B-class), Hermes’s tool-calling and long-context abilities sometimes fail. Users have reported that running a workflow on a lower-tier model might not properly call an API or keep track of tool usage. For example, one user noted that Hermes “calls a tool once then forgets how to use it” when using a 7B model.

Impact: Low. Most core complaints are about the agent itself, but a few users observed degraded performance with weaker models. Since Hermes is heavily tested on larger (often cloud) models, using it with minimal models can expose failures. However, this is more a model-limit issue than Hermes itself.

Examples: (Reported in Chinese forums) One user said small models sometimes “just call a tool once and drop it,” meaning they had to restart tasks. Others noted that skill generation works best with big models only. These comments appear in a few threads comparing model performance.

Workaround/Response: The official advice is that Hermes performs optimally with sufficiently powerful models; for smaller ones, avoid workflows requiring complex, multi-step tools. As a fix, users either upgrade to a better model or narrow their tool usage. The Hermes docs and changelogs hint that they will refine multi-provider support to better handle low-memory models, but no concrete solution is yet offered.

14. Telegram/External Messaging Bugs

Issue: Some reported issues specifically with external channel integrations, especially Telegram. For example, earlier versions had a bug where a Telegram bot token was incorrectly truncated or copying problems. Users on Telegram complained they had to re-enter gateway tokens because the saved token got cut off.

Impact: Low. It was a channel-specific quirk. A few GitHub issues and forum posts show Telegram setup failures (usually fixed by providing newer patches). Other integrations (Discord, Slack) did not have as many bug reports.

Examples: (From multilingual GitHub issues/user Q&A) There were reports of Hermes throwing errors on gateway start due to invalid tokens. The community recommended regenerating the token with correct permissions.

Workaround/Response: These were largely one-time fixes. The Hermes core devs merged patches in mid-2026 to streamline the token parsing, and recent releases (v0.5+) no longer truncate tokens. If you see a Telegram error, upgrading your Hermes CLI or following the “hermes gateway restart” procedure solves it.

15. Docker & Deployment Quirks

Issue: A few early adopters tried running Hermes via Docker or on special platforms and encountered incomplete support. For example, Docker images were initially missing some dependencies, meaning you had to install additional tools manually inside the container. Similarly, Windows or Termux installations occasionally had missing features (notifications, voice tools).

Impact: Low. Most of the core user base runs Hermes on Linux or WSL, so these deployment issues only affect edge cases. They did show up on GitHub and community posts, but were quickly patched by v0.6.0.

Examples: In Reddit’s technical threads, one user noted “Docker support was incomplete at first” and was relieved when a later release addressed it. Another mentioned having to apt-get extra packages in Docker to get full functionality.

Workaround/Response: The Hermes team acknowledges all platforms where Hermes should run. The solution has been iterative: the official Docker image and installer script now handle most cases automatically. The docs even have a “Tier 2” note on Termux/Android support. Users on those platforms are told to stick to recommended install steps. Today this is largely moot for most users.

16. OpenAI Codex Integration Error (Now Fixed)

Issue: In May 2026, several users found that using OpenAI’s Codex (via the Nous Portal) caused a “NoneType” crash. In other words, trying to use Codex as the LLM backend resulted in an error “'NoneType' object is not iterable”, halting Hermes. This was a sudden regression after an OpenAI API change.

Impact: Low (temporary). It affected any Hermes user relying on the Codex API (often for free or cheaper large models). For a period of days, those users could not run Hermes at all without this fix. Many forum posts and the NousResearch Discord discussed the outage.

Examples: A Korean inflearn Q&A captured this: dozens of people noted Hermes+Codex gave the exact same NoneType error. The question “Hermes + Codex NoneType error [KR]” linked to a GitHub issue (www.inflearn.com).

Workaround/Response: NousResearch quickly merged the fix. The GitHub issue 32956 was closed on May 27, 2026, and users reported that simply pulling the latest version or reinstalling patched the problem (www.inflearn.com). (The inflearn post says “the fix was merged back into main - no separate patch needed.”) So by v0.14.9 everyone could use Codex again. This shows the responsiveness of the team, but it counts as a “big problem” because it did stop workflows for Codex users in practice.

17. No Built-In Multi-Agent Support (Profiles Added)

Issue: (Closely related to issue #10) Hermes initially had no built-in way to run different agent profiles simultaneously beyond CCI multiple processes. This meant, for example, you couldn’t easily run one Hermes as a “research bot” and another as a “assistant” on the same machine.

Impact: Moderate. It was essentially the same gripe as single-agent above, so many users lumped this under “single agent design.” We include it to note the recent official response.

Examples: Community questions asked “How do I run multiple Hermes agents in parallel?” Official answers pointed to the new “profiles” feature. The docs now explicitly cover this use-case (hermes-agent.nousresearch.com).

Workaround/Response: As of mid-2026, Hermes natively supports profiles. Creating a new profile (e.g. hermes profile create coder) gives you a separate Hermes instance with its own config and memory (hermes-agent.nousresearch.com). This effectively lets you have many agents on one host. The documentation shows exactly how to set this up. In short, this concern has been addressed by the developers (so severity is now low), but it was a notable issue for early adopters.

18. Android/Termux Installation Issues

Issue: Running Hermes on Android (via Termux) or similar non-standard platforms sometimes failed. A few users tried installing on phones and hit issues with the installer script or missing binaries.

Impact: Low. This affects only a tiny fraction of users (those on Termux/Android). It was mentioned in some GitHub issues and forums, but never became a mainstream complaint.

Examples: GitHub issue comments note that hermes setup on Termux could fail to start properly if dependencies aren’t met. The official docs even call Termux “Tier 2 – best effort only” (hermes-agent.nousresearch.com).

Workaround/Response: The developers recommend sticking to desktop OS (Linux/WSL/Mac/Windows). If on Termux, one must follow the manual steps in the docs. The community has a few threads on how to fix Android-specific problems, but this was never a Hermes-specific bug so much as a platform limitation. It ranks near the bottom of impact.

19. “Stuck” or Erroneous Memory Persisting

Issue: A couple of users mentioned worries that once the agent learns something wrong (see #9), that memory might get “stuck” and not be easily deleted. For example, if a task “bombed” but was persisted, it could continue to influence future behavior.

Impact: Low. This is more a subtype of issue #8 and #9 than a separate bug. It came up in a few blog comments (“if a failed skill is saved as memory, can we clear it?”) but there were no large threads focused on it. We list it for completeness.

Examples: In the earlier quote (linux.do), a user worried “if a task fails, won’t saved memory pollute the model?” This concept appears sporadically in forums. No widespread evidence of irrecoverable “stuck” knowledge has emerged, however.

Workaround/Response: Hermes provides commands (/memory reject, /memory approve) to remove unwanted memories manually. The short answer from developers is that once written, memories persist unless explicitly deleted. Users are encouraged to carefully curate or reset memory if incorrect data was stored.

20. User Interface Limitations (CLI vs. GUI)

Issue: Some users (especially new ones) have asked for a more user-friendly interface. Initially Hermes was CLI-based (with a terminal UI), so it lacked the kind of visual chat or dashboard UI users expected from consumer chatbots. Before v0.9, there was no native browser or mobile interface built in, which turned off some non-technical users.

Impact: Low-to-Moderate. This isn’t a bug but a UX issue. Many Redditors and X users mentioned “do you have a windowed GUI?” as a question. It became less of an issue after Hermes introduced a Desktop app and an experimental “Kanban dashboard” later in 2026. But early on, some users panned it as “CLI-only.”

Examples: On r/AI_Agents and on Chinese forums, newcomers asked if Hermes had a web chat or configuration page (like OpenClaw). Answers often pointed to community-built tools or suggested waiting for future features.

Workaround/Response: Now, Hermes has an official web UI. The Hermes Dashboard (accessible via hermes dashboard, see OpenClaw’s guide (openclawlaunch.com)) provides a browser interface with chat, skill management, and logs. In mid-2026 the NousResearch team even released a desktop app with a chat window. These additions address the concern, but users have to upgrade to v0.9+ and use those commands. In summary, Hermes is no longer just CLI, but this was a pain point early in adoption.

Conclusion

Across Reddit and X, sentiment about Hermes is a mix of amazement and frustration. Users consistently praise its innovative learning model and ease of initial setup, but many of these issues above show a community still wrestling with “version 1.0” rough edges. The top complaints (self-evaluation flaws, skill overwrites, limited integrations) reflect core design trade-offs in Hermes’s architecture. Happily, the pace of development has been brisk: several of the above problems (multi-agent profiles, GUI dashboards, Codex bugs) have seen partial or full fixes in recent releases. As of summer 2026, the tone is cautiously optimistic – “Hermes is exciting but still bleeding-edge.” Many threads express frustration with Hermes no more, but with the early hype (e.g. astroturfing counter-claims). Overall, the community appears patient: they recognize many issues are being worked on. But it’s clear that every new feature or claim promptly triggers fresh discussion. In short, Hermes’s user base is vocal: they’ve made the biggest problems known, and the project’s future updates will surely take these into account.