How Sherwood Uses Hermes as a Personal Agent for Inbox Triage
Built by Sherwood · · Source: X
Result: After a week, Sherwood says they're a fan. More and more of their work now happens in Discord with Hermes, and phone calls got much better once Hermes started reviewing each call and fixing its own mistakes.
What they built
Sherwood has used Hermes as their personal agent for about a week. Hermes runs on Railway and reaches all of Sherwood's tools through an MCP gateway Sherwood built: email, calendar, Slack, X, LinkedIn, GitHub, Obsidian, DNS and others. It runs code in a separate Vercel sandbox. According to Sherwood, it's been most useful for inbox triage, a morning brief and evening recap, prospecting and sourcing, side projects, and tracking and landing PRs.
How it works
- Discord as the main interface: Sherwood started on Telegram but switched to Discord after a few days. They say Telegram lacked threads and channels and its mobile app was buggy. Now each area (email, X, GitHub, calendar, reminders) has its own channel, and Hermes posts updates there through the day.
- Slack, locked to one person: Hermes is in the team's Slack workspace but only responds to Sherwood. It ignores DMs from anyone else and only replies in channels when Sherwood tags it, so teammates and Slack Connect customers can't reach Sherwood's inbox through it.
- Approved replies: Hermes drafts replies across email, Slack, LinkedIn, X and iMessage, and Sherwood approves them one at a time.
- Obsidian as a notebook: A small MCP server gives Hermes read/write access to Sherwood's cloud-synced vault. Hermes keeps a note on each person Sherwood deals with, writes a nightly recap, and saves documents like PRDs.
- Shared memory: Sherwood built a memory store on Railway, exposed over MCP, that Claude Code, Codex, Cursor and Hermes all read and write. On first launch, Hermes onboarded itself by reading those memories.
- Voice and phone: Sherwood mostly talks to Hermes with voice notes or Wispr Flow. Hermes can also make and take phone calls through Vapi, and it reviews each call afterward to find and fix problems.
The result
Sherwood says Hermes keeps getting better because it saves their corrections to memory. Having no sessions makes it feel like it has unlimited context. Their TLDR is that they're a fan.
How to build something similar
- Put your tool connections behind one MCP gateway so each agent doesn't need its own set of integrations.
- Give each area its own channel or thread so updates are easy to scan.
- Have the agent draft outgoing messages for your approval, and only respond to you in shared workspaces.
- Keep memory in a shared store that every agent can read and write, and save corrections there as you make them.
The original post
I've been using Hermes as my personal agent for about a week now. Some observations: 1- My setup is a little unusual. Hermes runs on @Railway and connects to all of my tools through my own MCP gateway (email, calendar, Slack, X, LinkedIn, GitHub, Obsidian, DNS, etc). It runs code in a separate @vercel sandbox. 2- I started out communicating w/ my Hermes agent on Telegram but moved to @discord after just a few days... Telegram doesn't really do threads or channels, and honestly the mobile app was so buggy that it was hard to use. In Discord I have a channel for each area (email, X, GitHub, calendar, reminders...) and Hermes posts updates there throughout the day. 3- I also added Hermes to the @sazabi Slack workspace so that I can communicate w/ it in full-view of my team. The catch: it ONLY responds to me. It ignores DMs from everyone else and only replies in channels when I tag it. I didn't want my teammates (or customers in Slack Connect channels) to be able to get at my inbox through it. 😅 4- I gave Hermes access to my @obsdmd vault; it uses Obsidian like a notebook. My vault is synced to the cloud and I run a small MCP server (vault-cortex) that gives Hermes read/write access. Hermes keeps a note on every person I interact with (built from my Slack, email, meeting notes and WhatsApp), writes a recap of my day every night, and saves things like PRDs. 5- I also built my own memory system, which is also hosted on Railway + exposed to all of my agents over MCP. Claude Code, Codex, Cursor and Hermes all read from and write to this one memory store. The first time I started Hermes, it onboarded itself by reading all of these memories, which was pretty sick. 6- Things Hermes has been most useful for: - inbox triage (it drafts replies and I approve them one by one; I am not just triaging my email inbox, but also Slack, LinkedIn, X, iMessage, etc.) - morning brief + evening recap - prospecting/sourcing - working on side projects - tracking and landing PRs 7- Because Hermes triages + summarizes so many different inboxes for me, I find that more and more of my "work" happens in Discord; I'm just talking back and forth w/ Hermes all day. 8- I mostly interact w/ Hermes using voice notes or @WisprFlow , but it also has the ability to "talk" w/ me over a regular phone call w/ @Vapi_AI . It supports both inbound + outbound calls. The first few calls were kinda rough so I configured Hermes to reviews every call afterwards, reflect on what went wrong, and implement fixes. It's working way better now. 9- One obvious but huge part of Hermes that gives it the edge over local coding agents: it keeps getting better. Every time I correct it or give it some info about how to perform a task, it saves this to memory and references it in the future. Other coding agents do this too, but Hermes seems to do a better job of "learning" and getting smarter over time. Also, because there are no "sessions" , Hermes gives you the feeling of infinite context, which is really nice. This post got way longer than expected, but there ya go. My impressions from one week w/ Hermes. TLDR - I'm a fan. I am tempted to spend more time w/ other personal assistants like @Muse and @instinct_xyz but , to be honest, after seeing a post from the @NousResearch team about how "Hermes will always be for power users", I am doubtful that I will prefer either of those...
Want to build something like this?
Join the Shipping Skool community free. Paid members get live bootcamp calls every week.
Join Shipping Skool — FreeMore use cases
- How Vinay Moved an AI Second Brain from Claude Code to Grok BotPersonal Productivity
- How Evan Kirstel Uses Claude Cowork as a Help Desk for Mac and iPhonePersonal Productivity
- How Khe Hy Built an Ambition-Upgrade Skill for Prompts and TasksPersonal Productivity
- How Mike P Rebuilt His Grok Bot Agent Setup in Meta Muse to ComparePersonal Productivity