| topic | agents |
|---|---|
| type | guide |
| status | research-complete |
| last-validated | 2026-05-21 |
| original-query | r/hermesagent subreddit context - NousResearch project, different from ZAO Hermes, naming collision only (reconstructed) |
| related-docs | 483, 529, 531, 541, 547 |
| tier | QUICK |
Clarify: r/hermesagent is NOT ZAO's Hermes. It's a community subreddit for NousResearch/hermes-agent, a different autonomous coding framework. No branding conflict, but naming collision exists.
r/hermesagent is a subreddit for NousResearch/hermes-agent (GitHub: NousResearch/hermes-agent), an autonomous framework for code execution, debugging, and repository monitoring. Active community sharing automation patterns. Completely unrelated to ZAO's Hermes (autonomous fix-PR pipeline).
- Owner: NousResearch community
- Topic: NousResearch/hermes-agent framework - autonomous coding tasks, local LLM integrations, agent automation
- Sample posts: Daily update automation (cron job watching repo commits), desktop integration examples, provider configs
- Activity: Active - daily posts, real implementation sharing
- Sample thread: "The cron job every serious Hermes Agent user should probably have" (edoardo, Raspberry Pi 4 setup)
None. Different projects.
- ZAO Hermes: Autonomous fix-PR pipeline. Telegram bot. Claude models + MCP. Code coder-critic-auto-PR loop. Bot at @zoe_hermes_bot. Repo: bot/src/hermes/ (ZAOOS monorepo).
- NousResearch Hermes Agent: Autonomous framework for repo monitoring, code execution, provider integration. Open source. Desktop app integrations. Cron/local-LLM-based.
Both named "Hermes" independently. No cross-use, no integration need.
| Action | Owner | Type |
|---|---|---|
| No action - naming collision noted | Zaal | Resolved |
Inbox forward was legitimate context-building (agent frameworks), not a merge candidate.