Jonathon's AI Wiki

Hermes Agent — User Stories and Use Cases

6 min read

Source: Hermes Agent — User Stories docs (ai-research/hermes-agent-user-stories-2026-05-09.md; hermes-agent.nousresearch.com)

Nous Research’s official Hermes Agent docs include a community-curated User Stories & Use Cases page that catalogs feature requests, integrations, and real-world deployments — sourced from GitHub issues and X/Twitter posts. Useful as a roadmap signal (what users actually want) and as a deployment-pattern map (what Hermes is being used for in production).

Five categories

The page groups stories into five buckets, each of which surfaces a different aspect of the Hermes value proposition:

  1. Privacy & Self-Hosted — secure remote access patterns
  2. Business Ops — sales, sales outreach, inventory, email
  3. Integrations — protocol-level requests (JMAP, etc.)
  4. Personal Assistant — Google Tasks, productivity tools
  5. Meta & Ecosystem — migration paths from competing agents

A sixth category (General) holds testimonials.

Privacy & Self-Hosted

Tailscale serve for secure remote access (no exposed ports)

Users want secure remote access to the Hermes API server / Open WebUI without exposing ports publicly. Tailscale serve provides zero-config HTTPS tunneling over a private mesh — instead of port-forwarding 443 from a residential IP or running a ufw allow 443, Tailscale’s mesh network lets the operator’s laptop reach the Hermes box over an authenticated WireGuard tunnel.

This pairs directly with the Hermes seven-layer security model: layer 1-7 protect what runs on the box; Tailscale serve protects who can reach it.

— @artile, GitHub, 2026

Business Ops

Create and edit Google Slides decks

Extending the google-workspace skill to Google Slides so Hermes can create and edit presentations for users already in Google Workspace. Lifts Hermes from “creates Google Docs and Sheets” to “creates the full deliverable pipeline a sales/marketing function needs.”

— @PaulTisl, GitHub, 2026

Hunter.io email-finding for sales outreach

Surface Hunter.io (email lookup/verification) via Composio MCP for sales-outreach workflows. Closes the loop between LinkedIn/Apollo prospecting and email-on-file enrichment without a manual handoff.

— @m1chaeljmk, GitHub, 2026

Live inventory tracking on Hermes

With Hermes (built by @NousResearch) providing 40+ built-in tools, persistent memory, and subagent parallelization, the development experience is best-in-class. Built for operations like inventory tracking where context, memory, and real-time inputs are non-negotiable.

Real production deployment — not a feature request. Anchors Hermes’ positioning against shorter-context coding agents for stateful business workflows.

— @akashnet, X/Twitter, 2026-04-21

Give your Hermes its own email inbox

Here’s how to give your Hermes agent its own email inbox. No SMTP/IMAP, no Google OAuth, just plug in AgentMail using MCP.

AgentMail provides a hosted email inbox over MCP — agents get a real address without the operator wiring SMTP credentials into the box. Pairs with the MCP credential scoping rules (the AgentMail credential goes only to that MCP subprocess).

— @agentmail, X/Twitter, 2026-04-07

Integrations

JMAP email for Fastmail users

Requesting JMAP support in the email integration for Fastmail users. JMAP is the modern HTTPS-native replacement for IMAP — more efficient, batchable, and what Fastmail-as-an-IMAP-source actually wraps internally. For agents that read/triage email at scale, JMAP collapses dozens of IMAP roundtrips into a single batched HTTP call.

— @zednik-max, GitHub, 2026

Personal Assistant

Google Tasks integration

Adding a Google Tasks tool so Hermes can create, update and list tasks as part of personal productivity. Bridges the “agent did the work” → “next-action lives in my Tasks list” gap most users hit when they try to combine Hermes with their actual GTD pipeline.

— @isakcarlson5-del, GitHub, 2026

Sometimes Hermes Agent melts my heart

Sometimes Hermes Agent melts my heart @NousResearch.

Open-ended testimonial — not a feature request. Useful as a calibration on what people actually feel about the product.

— @flyingcloudliu-hub, X/Twitter, 2026

Meta & Ecosystem

Shadow-to-live migration from OpenClaw

A proposed migration path for users moving from OpenClaw to Hermes, covering shadow-mode runs before full cutover. Shadow mode is the pattern where the new agent runs alongside the old one, gets the same inputs, but doesn’t act — operators compare outputs and only flip the cutover when shadow runs match for N consecutive days.

The OpenClaw → Hermes pattern matters because Printing Press, Crabbox, and several other tools in this wiki ship as OpenClaw plugins — operators committed to OpenClaw’s plugin ecosystem need a path that doesn’t drop those integrations.

— @oangelo, GitHub, 2026

Switched from OpenClaw, not looking back

A real cutover testimonial. Counts as social proof for the migration story above.

— @pfanis, X/Twitter, 2026-04-14

General

An AI employee for my hardest tasks

Hermes Agent with ChatGPT 5.5 is literally magic. I’ve thrown some of my hardest tasks at this combo and the agent has been able to handle EVERYTHING. Time to set up your AI employee.

Validates the Hermes + ChatGPT 5.5 stack pattern that Nate Herk’s course walks operators through end-to-end.

Patterns to draw from this catalog

Reading the full list of user stories surfaces three operational patterns:

  1. The Hermes value prop is “stateful business agent,” not “coding agent.” Inventory tracking, sales outreach, email triage, Google Tasks — these are workflows where the long-running memory + multi-day session continuity matter more than raw code-generation speed. Treat Hermes as a Managed Agents alternative for self-hosted ops, not as a Claude Code competitor.
  2. MCP is the integration substrate. Hunter.io via Composio MCP, AgentMail via MCP, Google Slides extending google-workspace skill — every new integration ships as either an MCP server or a skill that wraps an MCP server. Operators looking to extend Hermes should design MCP-first.
  3. Migration from OpenClaw is real. OpenClaw → Hermes via shadow mode is a documented path. The reverse (Hermes → OpenClaw) is not. For operators committing to one ecosystem, this is a directional signal.

Try It

  1. Browse the live page at https://hermes-agent.nousresearch.com/docs/user-stories — it updates as community contributions land. The cohort of items above is a 2026-05-09 snapshot.
  2. Submit a use case by opening a GitHub issue on the Hermes repo or tweeting @NousResearch with the use case. Repeat patterns drive prioritization.
  3. Test the AgentMail MCP if you want Hermes to handle email without wiring SMTP. Search “AgentMail MCP Hermes” — there’s a published recipe.
  4. Set up Tailscale serve before exposing Hermes’ Open WebUI publicly. The tailscale serve documentation walks the zero-port-forwarding pattern.
  5. For shadow-mode migration, run both agents in parallel against a non-mutating workflow first (e.g., a daily briefing). Compare outputs for a week before cutting any production workflow.

Open Questions

  • How fresh is the user-stories page? It pulls from GitHub issues and X — is it auto-synced (atom feed?) or manually curated? If manual, the 2026-05-09 snapshot may already be stale.
  • Are upvotes/likes tracked? The page doesn’t show signal density, so a single tweet ranks alongside a 50-thumbs-up GitHub issue.
  • Does Nous publish a roadmap that links explicit user stories to upcoming releases? If yes, that’s a higher-signal artifact to track.

Graph View

Backlinks