Hermes
You wake up, and before you’ve touched your phone, Hermes has already read the news, scanned your portfolio, checked what your competitors launched overnight, compiled it into a PDF, and dropped the whole thing into your Telegram. Zero prompts. Zero tabs. Zero minutes of your morning.
That’s not science fiction. That’s what we’re building here.
But to get there, we need to be clear about something: what you’re building with Hermes is not a chatbot. The distinction matters, and most tutorials skip right past it.
A Chatbot Responds. An AI Agent Acts.
Think of a chatbot like a brilliant librarian who only works on one request at a time. You walk up, ask a question, they answer, and the interaction is complete. They have no idea what you asked yesterday. They don’t remember your preferences. When you come back tomorrow, you’re a stranger.
An AI agent is more like a capable employee. You give them a task and they figure out the steps themselves. They pick the right tools, execute them in sequence, read the results, decide whether the task is done, and loop back if it isn’t. They remember what you worked on. They build skills. They get faster the more they do a particular job.
Hermes was built by Moose Research specifically for that second model. What makes it different from most agent frameworks isn’t the UI or the model support. It’s one architectural decision: every time Hermes finishes a task, it writes down what it learned.
It creates a skill file. A set of reusable instructions, specific to that exact type of work. The next time you ask for something similar, Hermes doesn’t figure out the process from scratch. It reads its own notes. And those notes rewrite themselves over time based on how you actually use the system.
That is the core architecture which we will unpack in the rest of this article.
Here is a video to check out as well.
Why Your Current AI Setup Has Amnesia
Here’s the problem with Claude, ChatGPT, and most AI tools: every new conversation starts from zero. You’ve explained your content style a hundred times. You’ve described your workflow, your preferences, your project names, the specific tone you like for email replies. Every single session, that context evaporates.
This isn’t a bug exactly. It’s a design decision. These systems are optimized for breadth across millions of users, not depth with any single one. They can’t afford to know you specifically.
Hermes is built around the opposite bet. It accumulates a profile of you across sessions: your preferences, your content style, your recurring workflows. You can even feed it your website and ask it to run a web search on you. Hermes builds a soul.md file that captures who you are and how you want things done. A week in, it knows you. A month in, it has context on your projects.
Three things make Hermes structurally different from what you’re probably already using:
