HERMES.WORKSPACE
I run a self-hosted personal agent that reads my mail, watches sources, maintains my knowledge base, and reports back to me. This is how I use it.
My deployment of Hermes Agent, an open-source platform built by Nous Research. It is their platform, not mine.
HERMES / WORKSPACE01 / THE WORK
Not a demo. These are the jobs my agent actually does for me.
About two dozen cron jobs run on my behalf: a morning briefing, feeds and news watched and summarised, weekly knowledge-base synthesis, session housekeeping, and checks on its own credentials.
SCHEDULED ROUTINES
It searches, triages and extracts from my Gmail through Google Workspace tooling, and turns financial statements and receipts into a local ledger.
GMAIL / LOCAL LEDGER
It maintains my Obsidian vault, flags contradictions instead of overwriting them, works on authenticated websites when there is no API, and manages my VPS, domains and services.
OBSIDIAN / INFRASTRUCTURE02 / UNDER THE HOOD
A practical setup, not a black box.
Skills, tools and plugins make the system useful. I keep the pieces swappable, and the credentials out of plain configuration.
Read the Hermes docsSkills I write task-specific markdown packs, loaded only when relevant. Dozens are in use, from energy-meter readings to marketplace messages and train times.
MCP servers I connect hosting, storage and other systems through documented Model Context Protocol interfaces.
A vault plugin I wrote keeper-vault-hermes to pull credentials from a managed vault rather than keep them in plain config.
03 / ASK
Questions go to my public SuperMe profile (superme.ai/ddimitrov) through this site's own server. Nothing is sent until you press Ask.
04 / PRIVACY
This site has no cookies, no analytics, no external scripts and no third-party embeds. The one exception is the Ask box: if you press Ask, your question is forwarded by this server to my SuperMe profile (superme.ai) and the answer comes back. I do not log visitors; SuperMe may keep the question.