# Grok Bot vs Hermes Agent

Comparison for Josh D, who already runs Grok Bot (Researcher + Signal Monitor). Grok Bot is a managed Cursor/SpaceXAI teammate product on a shared cloud computer; Hermes Agent is a self-hosted open-source agent OS with messaging gateways and cron.

Tags: comparison, grok-bot, hermes-agent, decision

## Summary

Keep Grok Bot for connector/computer-use and multi-Bot orchestration. Add Hermes when you need self-hosted Signal monitoring, explicit model control, cron digests, or git-backupable memory/skills. Do not treat either product’s “separate agents/bots” as a security boundary without separate hosts/profiles.

## Matrix (short)

| Dimension | Grok Bot | Hermes Agent |
|---|---|---|
| Shape | Managed Bots + shared Agent Computer | Self-hosted CLI/TUI/Desktop/gateway |
| Data | Cursor-hosted; Legacy Privacy Mode blocked | Local `~/.hermes` / Docker volume |
| Models | No picker; router | BYO / Portal / local |
| Signal | Not signal-cli host | First-class Signal adapter |
| Schedule | Routines | Rich cron (+ no-agent scripts) |
| Multi-agent | Bots + group chats | Subagents, Kanban, profiles, A2A |
| Ops | Low | Medium–high |
| Best Josh use | Researcher / SaaS computer-use | Signal Monitor / nightly research automation |

## Recommendation

1. Keep Grok Bot Researcher.
2. Pilot Hermes for Signal Monitor + cron if willing to run signal-cli + gateway hardening.
3. Hybrid: Hermes writes briefs into research-wiki / Signal → Grok Bot synthesizes with approvals.

## Related

- [[hermes-agent]]
- [[grok-bot]]
- [[grok-bot-privacy-and-security]]
- [[youtube-hermes-kanban-multi-agent]]
- [[youtube-hermes-desktop-plugins]]
- [[youtube-ai-code-review-bot]] (Eve as a third Slack/GitHub agent shape)
- raw/`hermes-agent-2026-08-12/comparison-grok-bot.md`

## Sources

- Local wiki Grok Bot pages (2026-08-12 ingest)
- Hermes official docs + v2026.8.3 release notes (see raw pack `sources.json`)