This is my current setup for using Hermes Agent as a personal assistant. I hope someone will find this useful and get some ideas out of it.
I have two Hermes instances: one on an always-on host and another running on my Mac. Both read from and write to a single Obsidian vault of plain Markdown notes that serves as shared memory and a set of operating instructions. I’m using a Discord server to communicate with both instances and allow them to collaborate with each other.
This is what a day with it actually looks like, and why each piece is built the way it is.
An inbox that reads itself, quietly
An inbox assistant wakes every five minutes, and most of those wake-ups cost nothing at all. Before the agent starts, a small script checks whether any message in the window is genuinely new. If everything has already been recorded, the run stops there: no model call, no prompt, no notification, no bill. That gate is why a five-minute cadence is affordable rather than extravagant, and it is also why the channel stays quiet. Silence is not a failure state here; it is the normal one.
When there is something, it reads the whole thing: the body, the thread, and the attachments. A PDF, a Word file or a spreadsheet is converted to text and scanned for deadlines or anything I am being asked to do. Email senders are matched against my contacts, so the notification names the person and their company instead of just an address. It reads my own sent mail as well, since that context may be important.
For any message that plainly requires an answer, the assistant writes the reply. It reads the entire thread first, and it checks whether I have already answered in that thread. If I have, it leaves the message alone and says so. If I have not, it writes a reply on my behalf: same thread, correct recipient, the other people from the original message carried into Cc so nobody quietly drops off a group reply, and the signature already attached. The draft is sitting in my drafts folder, already addressed and signed. The notification tells me who it is for and links to it. All that is missing is my decision to send or edit the draft. The module that creates drafts has no ability to send at all.
The restraint matters as much as the writing. It will not draft a reply to a receipt, a notification, a newsletter, an authentication code or anything personal and sensitive. It will not invent a price, a date or a commitment to make a reply look complete. If the facts are missing, it drafts nothing and asks me instead.
Email communication
The assistant has its own email address on my domain, and how it treats a message depends entirely on where its own address appears:
Addressed to it directly: it reads, reports, and prepares an answer as an unsent draft, then waits for my word. Nothing goes out on my behalf.
Copied in: it may answer by itself, briefly, as itself, answering only what was asked of it and committing me to nothing.
Blind copied: it notes the message and never answers. A blind copy is information, not a question.
That middle case is the only standing permission it has to speak in public, and it is deliberately narrow: no prices, no deadlines, no facts about me or my business, and never anything based solely on the word of somebody who is not me.
From mail to commitments
Every message carrying a real date becomes a calendar event, on the calendar it belongs to. Every request for action without a date becomes a task instead, never both, so nothing is recorded twice in two places.
Automated notices I get by email never become tasks. A booking confirmation, even forwarded by somebody else, goes on the calendar like any other.
Scheduling with clients
Meeting scheduling is the workflow I most wanted to hand over, and the one with the most rules. I copy the assistant into the client’s email thread and tell it to find times. It reads the thread, works out how long the meeting needs to be and whether the client asked for a certain date range or suggested time, like ‘next week’, then looks for slots that are genuinely free across all three of my calendars. What comes back is a short, friendly email to the client, offering real options, with me copied in. When the client picks one, the assistant checks the slot again before booking, creates the event with a Google Meet link, a one-hour-before reminder and the attendee list, then confirms it to the client and me.
I move between different time zones, so I had to set availability windows in both my time zone and the client’s. The agent reconciles those windows and takes them into consideration when suggesting times.
The 05:00 briefing
One briefing arrives before five in the morning, short enough to read in a minute: today’s and tomorrow’s events with conflicts flagged, the weather for wherever I actually am, the handful of emails that need me, anything due or overdue, and the day’s language drill and word of the day. I’m studying French, Italian and Portuguese, so the agent adds a word of the day to my briefing (I study different languages on different days). It has to be a word connected to my work or interests. I’ll explain the language drills below. The weather is the interesting part. Instead of assuming a city, it detects my location and cross-checks it against confirmed travel, so the forecast follows me rather than the server.
Language drills
A weekly job builds a bank of practice passages in French, Italian and Portuguese and renders each one to audio. Every morning before five, a script posts one drill: the text, the recording, and a slowed-down copy for the parts I am still struggling with. The language is chosen according to whichever language task is due. As I mentioned, I study each language on specific days of the week. The drills, like the word of the day, are based on my interests, real work or personal situations.
If I send a voice note reading the passage, the assistant transcribes it two or three times, compares the transcriptions so it does not correct me for transcription mistakes, and corrects me sentence by sentence against the passage itself. Generating the drills costs one model call a week; everything else in that process is handled by scripts.
Reminders
I ask the agent using voice or text in Discord to remind me of something, and it looks the person up if I mentioned someone, creates the task with a date (a task with no date is invisible to me, so today is the fallback), sets the reminder and reports what it created.
Credit card dates: a daily check keeps statement cut-off and payment dates visible and checks them against a ledger of what has actually been paid. The agent reminds me of upcoming payments.
Final notes
Behind all of it sits one Obsidian vault, and the rules for writing to it are stricter than anything else here. Routine automatic writes are limited to dated observations and clearly sourced snapshots of my current situation. Biography, decisions and anything sensitive need my approval, tied to the exact content proposed, so nothing is promoted quietly by an agent that liked its own idea.
None of it is clever. It is a great deal of unglamorous specificity, and the specificity is what makes it useful. The impressive thing is not that it can do a hundred things, but that the fifty small decisions about how it does them were made before I needed them.