When should you use it?
- Your best ideas arrive away from the desk
- You keep notes in plain Markdown files
- You like tinkering with self-hosted tools
Not for: People who want a polished consumer app; Anyone unwilling to let an agent edit their notes
What do you need, and what do you get?
You need
- A self-hosted agent reachable from a chat app
- An Obsidian vault
- Voice notes from your phone
You get
- Transcripts saved in a scratch area
- A structured outline with linked context
- An agent draft kept separate from your writing
How does it work, step by step?
- Start with an empty vaultThe author advises against importing years of old notes on day one.
- Connect a chat channelLet the agent receive voice messages from a messaging app you already use.
- Define the note shapeRaw transcript, cleaned argument, related links and a clearly marked agent draft.
- Write the final version yourselfUse the draft to react to, not to publish.
- Add one use at a timeHe later added a coaching plan that adapts to short days and a recipe collection from photos and messages.
The prompt
Our own prompt, inspired by Mete Polat and written to work in Custom agent. Values in lime are placeholders.
When I send you a voice note, transcribe it and save the raw text under Scratch in today's daily page of the vault. Then, in a separate Agent section, write a tidy outline of the argument, link up to [5] related notes from the vault, and add a short draft clearly labeled as yours. Never edit text outside the Scratch and Agent sections.
Inspired by Mete Polat: My Hermes & Obsidian Setup and Use Cases. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- By his own account the setup is rough, and he doubts most readers need it today.
- Lowering friction for the agent can make the vault harder for you to edit by hand.
Our take
Product designer Mete Polat sends messy voice notes to his Hermes agent over Telegram while walking his dog; by the time he sits down it has filed raw transcripts, a tidied argument, related links and a draft into an Obsidian note, while he still writes the final piece himself. The same setup later grew a fitness coach and a recipe archive. We like how clearly he keeps his own writing separate from the agent's draft; that boundary is what keeps the voice his. Starting with a blank vault is good advice for any knowledge-base project. Put the agent's output in a dedicated section so you always know which words are yours. Back up the vault before giving any agent write access. Add one use at a time rather than wiring every life domain on day one. Review transcripts for dictation errors before ideas harden into notes. Keep Telegram access tokens rotated and the chat private.
Where the time goes back: The gap between a spoken idea and usable material closes while you are away from the keyboard.
FAQ
Does the agent write his articles?
What if I want something simpler?
Source and credit
Inspired by Mete Polat. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- My Hermes & Obsidian Setup and Use Cases
- Creator
- Mete Polat
- Published on
- metedata.substack.com (Substack)
- Original date
- May 20, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.