My Hermes Agent setup for running the office side of a commercial film company
I own Aumen Film Co, a commercial production company. Every finished film is still made by people with cameras, and I still go on set and make the work with crews. I use Hermes for the office around those jobs: production paperwork, sales follow-up, research, content, studio operations, and the records that keep the whole thing from living in my head.
I split the setup across Hermes profiles and scheduled workflows. Each role has its own instructions, tools, memory, and limits.
A few specific examples:
- Alfred is the front door. I can send a messy voice note after the gym, and he sorts it into the right projects, agents, and calendar items.
- Danny handles production operations. He helps build budgets and crew lists, turns photos of my marked-up schedules back into clean digital versions, prepares deal memos, tracks invoices, and runs finished files through an automated QA pass.
- George works on the sales side. He checks proposal status every business morning and drafts a follow-up when something has been sitting unsigned. Then I can edit if necessary and send.
- Truman (content agent) reads my call transcripts and hourly time logs, finds ideas worth coming back to, and puts them into a review queue. He also has access to a searchable catalog I built with a GUI for me and a CLI for agents of about 4,600 behind-the-scenes photos. It has face-matching done locally overnight when I bring in new images.
- Harriet and Q handle research and internal builds. Harriet runs stuff like last30days and firecrawl and sends lots of subagents, does synthesis, and preps research packets for other agents. Q has a bunch of watchdog crons, fixes or retools the other agents, does light building (usually for bigger builds I'm doing them in claude code or codex directly, starting with a PRD or similar from Q).
The profiles share an Obsidian vault with a number of source of truth files describing the company: how we work, the gear we own, our rules, our rates, and the things the agents might need to know. That shared context has been more important than any single model choice, and it's great to be able to swap models at any time or for specific tasks.
The permission structure matters just as much as the jobs. The systems start read-only, and some can graduate to drafts and approval queues. Sending, deleting, spending, and signing stay with me. For example, an e-signature send requires an approval code tied to the exact document I reviewed. If the document changes, the code stops working. George can draft and send contracts for e-signature, but only with that doc-specific code.
It has failed too. Nine scheduled runs died on the same login problem when I was trying to use Claude CLI, and for just over a week the only sign was a missing Friday report. Another time an agent told me an e-signature tool I was vetting included 25 free documents when the real number was three. Now a scheduled workflow also needs to tell me when it stops, and changing prices or limits are checked against a current source before anything acts on them.
I made a 14-minute walkthrough with the diagrams, the roster, some real examples, and the rules I use to keep the agents away from the parts of filmmaking I want people doing:
For people using Hermes profiles, are you giving each profile a narrow job, or keeping one general assistant and turning tools on only when needed? I am also interested in how other people monitor scheduled runs that fail silently.
Posted Jul 29, 2026, 1:07 PM UTC