HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NousResearch
hermes-agent
Python2026–2026
NousResearch / hermes-agent

hermes-agent

The agent that grows with you

22Distinct people
24Mentions
0Explicit recommenders
263KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The agent that grows with you

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week24 dated mentions

Observed mentions: 2026-03-05 17:08:51 UTC to 2026-10-03 20:22:36 UTC. Weeks start Monday, UTC.

01232026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 22026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-13 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-04-20 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-04-27 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsJun 152026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-21 00:00:00 UTC to 2026-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-28 00:00:00 UTC to 2026-10-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 28

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC110
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC220
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC000
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC101
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC202
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC000
Apr 132026-04-13 00:00:00 UTC2026-04-20 00:00:00 UTC211
Apr 202026-04-20 00:00:00 UTC2026-04-27 00:00:00 UTC101
Apr 272026-04-27 00:00:00 UTC2026-05-04 00:00:00 UTC101
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC000
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC101
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC110
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC101
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC101
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC303
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC000
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC220
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC000
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC211
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC202
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC000
Sep 212026-09-21 00:00:00 UTC2026-09-28 00:00:00 UTC000
Sep 282026-09-28 00:00:00 UTC2026-10-05 00:00:00 UTC101

What Hacker News says

24 sources
Sure, happy to provide you with an example of how to hold it (turns out Steve was right) =D https://github.com/NousResearch/hermes-agent is 99% (just a guess) LLM generated. 1140 closed pull requests this week. 1.5k closed issues. The github insights page for commits doesn't load for me presumably because it can't handle this scale of commits. But I estimate ~1K commits per day on average. There's a blog entry https://nousresearch.com/refactoring-hermes-with-1393-agents that details some work that was done by LLMs to refactor and improve the code. I guess they know how to hold it?
In Pop!_OS bans AI-generated code from much of its codebase
This is very similar to the mjrathburn openclaw incident several months back: https://theshamblog.com/an-ai-agent-wrote-a-hit-piece-on-me-... They discovered the agents started raising money for themselves, including crypto. https://pivot-to-ai.com/2026/02/16/the-obnoxious-github-open... Their iLands uses Claude and Codex, but their website says they will be using these too: https://github.com/openclaw/openclaw https://github.com/NousResearch/hermes-agent I've gotten more spam from academic research journals for uploading a handful of research preprints to open-access servers. In 3 years, I've gotten hundreds of emails that pass the spam filter. https://news.ycombinator.com/item?id=48542835 if the iLands emails are arriving from the same domain they can be blocked. If they are generating new sockpuppet domains, then it's a different issue
Read the rest
. Many of those addresses are untraceable or hard to trace. "Half a dozen" is not really above the threshold of annoying, but yes, if there's thousands of chat agents sending agents then it will be a major problem very soon. I noticed he placed them in the trash, not marked spam. If it's spam then mark it spam. All the domains show [agent]@ilands.app, so the domain can be blocked easily. I've gotten a ton of spam texts from the DCCC and a ton of robocalls that hang up after 10 seconds. Age old problems that haven't been fixed either. Update: Reddit had a thread on this a month ago: https://www.reddit.com/r/OpenAI/comments/1vn6tez/ai_research...
In The worst spam emails: iLands AI agent hustle
This is very similar to the mjrathburn openclaw incident several months back: https://theshamblog.com/an-ai-agent-wrote-a-hit-piece-on-me-... They discovered the agents started raising money for themselves, including crypto. https://pivot-to-ai.com/2026/02/16/the-obnoxious-github-open... Their iLands uses Claude and Codex, but their website says they will be using these too: https://github.com/openclaw/openclaw https://github.com/NousResearch/hermes-agent
In The Worst Spam Emails: Inside iLands' AI Agent Hustle
OpenCode seemed perfectly workable as a programming assistant. As personal assistants, they all fall short. It's too difficult to really shape their output. I was briefly impressed with OpenClaw a few times, but ultimately was turned off by not being able to get the models to stop being so damnably verbose. I thought I made progress for a while by having it tweak its soul, iterate, switch models, iterate, switch models, fuse the results, iterate... but ultimately it's all forgotten early in each session. And then one day it killed itself by rebuilding the container it was inside. Hermes apparently has some plagiarism issues they're trying to cover up [0] and I was deeply unimpressed with their janky, flickery CLI that force-enables a bulky obnoxious header on every launch. Hermes did readily dive into its own source code and did readily c
Read the rest
onfirm that there was no way to disable it. So that's neat. It constantly (wants to) run from upstream master which is unsettling. Nanoclaw and nanobot seemed fine, but not notably different. There were some common bugs and glitches that caused some minor data loss while configuring nanobot. After that I just deciding to start hacking my own together. What I really want in a harness is being able to actually control and rewrite the entire context window, like Zed's Text Threads before they obnoxiously and inexplicably removed what, to me, was their most powerful and distinguishing feature. [0] https://github.com/NousResearch/hermes-agent/issues/10232
In Hermes Agent – Open-source AI agent with persistent memory
I use PI ( https://pi.dev ) and ( https://hermes-agent.nousresearch.com/ ) as the main drivers together with deepseek-v4-pro as the main model (~10M/day tokens overall there). Hermes basically rules my personal life at this point - it is a _very_ useful personal assistant. I also use it at work (integrated at Slack) and at this point it answers most of both my emails and slack messages (I calibrated https://github.com/blader/humanizer with a large corpus of my own voice to make it less annoying for the others). My routine now involving walking in circles while exchanging messages with hermes directing it how to answer this or that... Hermes uses an llm-wiki ( https://gist.github.com/karpathy/442a6bf555914893e9891c11519... ) as a source of information when drafting suggested replies - I have a cronjob that feeds it all emails, slack messag
Read the rest
es, meeting minutes every single day. Claude Code with Opus 4.6 for multimodal/vision, design and writing tasks ("Create a crisp memo from this meeting transcription" is a prompt that will bring great results with either Opus 4.6 or GLM-5.1) - very recently I started to use https://github.com/anomalyco/opencode occasionally with opus models too (I am forcing myself a little bit because it is hard to help people with a tool you are unfamiliar with). For building software automatically I currently use one of the harness above for for launching https://tamandua-tetradactyla.nfshost.com/ feature-dev-merge-worktree runs (it provides workflows on top of PI+deepseek). Where it comes from: until recently I used https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16d... for automatic software building but while planning an AI bootcamp I concluded that teaching Gas Town along with everything else would be impossible (too hard/complex), and decided to teach https://github.com/snarktank/antfarm instead but did not want to add OpenClaw as one more dependency - so I built Tamandua ( https://github.com/igorhvr/tamandua ) and I ended up using it all the time! I now every single day before going to sleep launch a couple of runs and it is very cool waking up to see them done. For autoresearch-like, optimization, and other tasks with a very clear measurable goal (such as increasing test coverage, changing things from one programming language to another, etc) I use https://github.com/davebcn87/pi-autoresearch (100% of the time on top of deepseek-v4-pro). For debugging or very hard problems I use codex w/ GPT5.5. I don´t like its personality (lazy) but I do think it is smartest model available. As evidence, here is a commit of a problem where I tried Opus 4.8, Deepseek-v4-pro and a couple of other models and they all failed to understand what the bug was: https://github.com/NousResearch/hermes-agent/pull/38198/chan... - once the bug was found within codex I launched from it a tamandua bug-fix-merge-worktree run on top of deepseek-v4-pro that created the commit itself... As a web application I use OpenWebUI and I am specially fond of the notes feature ( https://docs.openwebui.com/features/notes/ ) which I did not find anywhere else. Last but not least, I love playing with local models. https://huggingface.co/Qwen/Qwen3-Coder-480B-A35B-Instruct is my current favorite for coding and deepseek-r1 for general tasks. I also started yesterday testing https://github.com/antirez/ds4 - it works _very_ well from what I could see so far. What comes next? Trying to figure out what is the "deepseek-v4-pro of multimodal" model (frontier performance, efficient/comparatively cheap to run, support for image/audio/video/etc). Currently using kimi-k2.6, will test Minimax M3 soon. Ah, almost forgot: https://huggingface.co/microsoft/VibeVoice-ASR will give you AMAZINGLY good meeting transcriptions (my hermes vibecoded a program to use it). Seriously, night and day difference from what the big players provide natively in their platforms. Have 8 people talking in 3 different languages? No problem - you will need a bit of patience and beefy hardware, only..
In Ask HN: What is your (AI) dev tech stack / workflow?
If I had to guess, this is a continuation of Anthropic's ongoing war to make third party tool usage go through per-token billing, specifically against a tool called Hermes-agent [0]. You can easily imagine why Anthropic might want to silently re-bill a customer violating their silly ToS restrictions and how an LLM told to implement the feature might arrive at this "solution". [0] https://github.com/NousResearch/hermes-agent
In HERMES.md in commit messages causes requests to route to extra usage billing

Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.