learn how to operate and master Hermes Agent. set up the agent control room template, configure specialist agents, and grow from one agent to a whole marketing company on one VPS.
hermes is an open-source autonomous agent by @NousResearch.
it runs on your laptop or a cheap VPS, remembers everything across sessions, and writes its own reusable skills as it works.
you control it through a terminal, Telegram, Discord, Slack, or email, whichever surface fits your workflow.
the core promise is compounding. on day one, hermes is a capable assistant. by day thirty, it has built a library of skills from your exact use cases, and repeating the same work gets faster and tighter every time.
Install Hermes in Two Minutes
run one curl command from the official Nous Research repo to install hermes. the installer pulls Node.js, Python dependencies, SQLite, and the hermes runtime automatically. the whole process takes under three minutes on a decent connection.
once installed, a setup wizard runs and asks which model provider you want. the three most common choices: anthropic (claude-sonnet-4, high quality), openai (gpt-5.4 with thinking mode, popular daily driver), or openrouter (qwen/qwen-3.5, free and capable for routine work).
after setup, run \hermes\ to open the CLI. give it a simple job first, something like "summarize my last five github notifications." if it responds with real output, your install is working. everything from here builds on that foundation.
Understand What You Just Installed
hermes stores everything inside \~/.hermes/\. skills it builds live in \~/.hermes/skills/\. session history is in SQLite with full-text search, meaning it can retrieve something you told it three weeks ago even if it is not currently in active memory.
memory works in three layers: short-term for the current session, working memory for important task context, and long-term through \MEMORY.md\ and \USER.md\ files. the agent reads these files at the start of every session to rebuild context.
the agent's identity lives in \SOUL.md\. this file is the equivalent of a system prompt written as a charter. it defines what the agent prioritizes, how it communicates, and what it avoids. write it before you start assigning real work.
Set Up Your Agent Control Room
a control room is one hermes profile configured to orchestrate everything else. create it with \hermes profile create control-room\. this profile holds no specialist knowledge, its only job is routing tasks to the right sub-agent and tracking results.
each specialist agent is its own profile with its own \SOUL.md\, its own memory files, and its own skill library. create a researcher profile, a writer profile, a scheduler profile. each one stays focused on a single domain and gets better at it over time.
wire everything together by enabling the \delegate_task\ tool on the control room profile. when you send the control room a job, it breaks it down and routes subtasks to whichever specialist is best suited. results come back to the control room, which assembles and returns the final output.
Connect Your Messaging Surface
the most useful thing you can do in the first week is connect hermes to Telegram. go to @BotFather, create a bot with a username ending in \_bot\, and paste the token into hermes gateway config. from that point, you can command your agents from your phone anywhere.
since all sessions share the same SQLite database, you can start a job in the terminal and check its status on Telegram without losing any context. the conversation thread is one continuous record regardless of which surface you used.
for team setups, create a shared profile on the VPS and grant team members access via the messaging gateway allowlist. this gives your whole team one agent they can all query without you building any custom UI.
Configure Scheduled Recurring Work
hermes has a built-in cron system. jobs are defined in \~/.hermes/cron/jobs.json\ using natural language frequency. the gateway checks every 60 seconds and runs due jobs in fresh, isolated sessions.
useful starting jobs: a daily briefing pulled from your configured sources at 8am, a weekly content draft generated from a topic queue, a nightly summary of any repo activity. each result delivers back to your Telegram or saves locally, whichever you set.
the key advantage of cron over manual prompting is that the agent builds skills from repeated job runs. after a few weeks of daily briefings, hermes knows exactly how you like them formatted and stops asking clarifying questions.
Grow From One Agent to a Marketing Operation
once the control room and messaging are working, add specialist profiles for each marketing function. a research agent that monitors competitors and trends, a writer agent trained on your brand voice, a scheduler agent that manages and posts content drafts.
teach each profile your style by feeding it examples early. run \hermes profile create writer\, then in the first session paste five pieces of content you have already written and tell it "this is the voice and format you write in." it writes a skill file from those examples automatically.
with four profiles running on a $6 VPS, one orchestrator and three specialists, you have the functional output of a small content team running 24/7. each agent compounds independently, and the control room coordinates the whole thing from a single command.
What Breaks and How to Catch It
the most common early mistake is skipping \SOUL.md\. an agent without identity is technically capable but inconsistent, it will handle edge cases differently each time and drift from your expectations without you noticing.
the second mistake is letting skills accumulate without reviewing them. hermes writes skills automatically, but not every skill it writes is correct. run \hermes skills list\ weekly and delete any that describe a flawed approach before the agent reinforces it further.
if a session runs long and starts producing worse output, context is filling up. use \/compress\ inside the session to summarize older context, or start a fresh session and let hermes pull what it needs from memory files. do not let degraded sessions run indefinitely.
The Operator Mindset
an operator's job is not to prompt. it is to define what the agents do, verify the output quality, and improve the skill library over time. the more precisely you define each profile's \SOUL.md\ and the more consistently you assign the right work to the right profile, the better every agent gets.
treat each profile as a hire. give it a clear role, examples of the work you expect, and time to build up its skill library before you judge its output. the compounding is real but it takes two to four weeks of consistent use to become obvious.
the agents do not replace judgment. they multiply the volume of work that your judgment can cover. your job shifts from doing the work to reviewing it, and that is the leverage.
if you read this far, follow @mikenevermiss for more amazing ai articles.
