Hermes

Hermes. We hold it under Tool in the garden.

Blurb

The agent that grows with you. Contribute to NousResearch/hermes-agent development by creating an account on GitHub.

Summary

Hermes targets the same problem space as OpenClaw: an always-available assistant across chat surfaces (Telegram, Slack, CLI, etc.) with memory, cron-style scheduling, and skill extensibility. It integrates Agent Client Protocol so editors like Obsidian can use the agent via plugins (e.g. obsidian-agent-client). On Apple Silicon, local runs via Ollama with models such as deepseek and qwen are practical.

Originally a credible competitor in the personal-agent wave; our position is that broad tool-and-shell access without tight policy boundaries is unsafe for most setups. Prefer IDE-bound agents (Claude Code, Cursor-class tools) or pipelines that emit reviewable scripts on a schedule.

Details

• Strengths: skill learning loop, multi-channel gateway, Agent Skills Framework portability, ACP for IDE clients, flexible model routing (cloud or Ollama).
• Risks: persistent credentials, messaging exfiltration, autonomous cron/subagent actions, treat as high-trust workload only with explicit sandboxing.
• When hold is OK: isolated experimentation, local-only models, single-user machine with clear data boundaries.
• When to avoid: production secrets on the same host, multi-tenant boxes, or “set and forget” automation without human review.
• Install: upstream documents quick install via install.sh on macOS/Linux; verify signing and update channel before production use.