Hermes Agent 0.6.0 Multi-Agent Profiles Update!

Key Takeaways

Hermes Agent 0.6 launches with multi agent profiles. You're leaving so much time on the table right now running one AI agent at a time when you could be running five. Every department doing its own thing manually, slowly, no coordination, no automation, just you doing the same tasks over and over. There is a better way and it just dropped. Hey, I'm the digital avatar of Julian Goldie and today we're breaking down Hermes Agent version 0.6, the update that finally cracks open multi agent automation for anyone willing to set it up free, open source, no subscriptions, just pure AI power running on your own machine. And I am going to show you exactly what changed, what it means for your workflows, and how you can actually start using it today. Stick around because the profiles feature alone is going to change how you think about AI agents completely. Let me start with the basics in case you've never heard of Hermes Agent. Hermes Agent is an open source AI agent built by Nous Research, the same team behind some of the most respected open AI models out there. It is self-hosted, you run it on your own machine, no monthly fee, no vendor lock-in. Connect it to whatever AI model you want, Open AI Claude via Nous Portal, any of the 200 plus models on Open Router, or even your own endpoint. Switch models with one command, no code changes. And it does not just sit in a browser tab. Hermes lives where you live. You can talk to it from Telegram, Discord, Slack, or WhatsApp. It It has persistent memory across sessions, it builds its own skills over time, and it can schedule tasks to run automatically, reports, backups, briefings, all without you lifting a finger. That is the foundation. Now, here's where version 0.6 gets really interesting. Before this update, Hermes had one major weakness and people in the community were very vocal about it. You could only run one agent at a time. Think about what that means in practice. You want an agent for customer support, another one for content drafting, a third one for research. With the old setup, you had to choose one agent, one config, one memory pool, everything mixed together. Open Claude, a competing open source agent, could run multi agent teams. That gap was a deal breaker for a lot of people doing teamwork flows or trying to automate multiple business functions at once. Version 0.6 closes that gap completely. Welcome to profiles. Profiles let you run multiple fully isolated Hermes instances from a single installation. Every profile gets its own config, its own API keys, its own memory, its own sessions, its own skills, and its own gateway service. When you create a profile, it instantly becomes its own command. Create a profile called Coder and you now have Coder Chat, Coder Setup, Coder Gateway, complete I grow completely separate from your main install. One for research, one for Slack, one for writing, zero crossover. And here is the safety layer that makes this actually production ready, token locks. If two profiles accidentally try to use the same bot token, same Telegram bot, same Discord bot, the second one gets blocked immediately with a clear error that tells you which profile already owns that credential. No silent failures, no weird behavior, clean clear separation. You can export and import profiles, too. So, if you set up an agent you really like, you can save it as a file and share it or move it to another machine. That is huge for teams that want consistent setups. Now, here is something a lot of people are going to miss about this release and I do not want you to be one of them. When I first started working with AI agents, the hardest part was not setting them up. It was knowing which workflows were actually worth automating and which ones would just waste more time than they saved. That is why I created a community called AI Profit Boardroom with over 2,000 members all focused on learning AI together and sharing what actually works. It is where I figured out which agent setups save real time versus which ones just look good in demos. The community shares real use cases and practical implementations, people who are actually building and testing these tools every day. If you are serious about using AI to improve your work and skills, check it out. Link is in the description. Okay, back to what is new in version 0.6 because profiles is only part of the story. Next up, MCP server mode. MCP stands for Model Context Protocol, a standard way for AI tools to talk to each other. With version 0.6, Hermes can now act as an MCP server. Run one command, Hermes MCP serve arm and your conversations, sessions, and full Hermes history becomes accessible from Claude Desktop, Cursor, VS Code, or any other MCP compatible client. Browse conversations, search sessions, manage attachments, all from inside the tools you already use. Supports both STDO and streamable HTTP transports. Now, let me tell you about something that seems small but is actually critical for reliability, fallback provider chains. Here's a situation. Your agent is running, it is handling tasks, and your primary AI provider goes down. Rate limit hit, server issue, outage. What happens? Before version 0.6, your agent just stops. Task fails. You have to notice, fix it, restart. Now, you configure a list of providers in order. When the primary one fails, Hermes automatically tries the next one. You set it up once in your config file. After that, it just handles itself. Your workflows keep running even when individual providers have problems. This is the kind of resilience that makes the difference between a toy and a real production tool. Now, let me walk through the new platform integrations because there are a few here worth knowing about. First, Feishu and WeCom. If you are working with Chinese enterprise teams, these are massive. Feishu, also known as Lark, is one of the biggest workplace communication tools in Asia. WeCom is enterprise WeChat. Both now have full gateway adapters in Hermes, message cards, group chat, image attachments, interactive callbacks, the full feature set. Second, Slack multi workspace. Before this, one Hermes gateway could connect to one Slack workspace. Now, you connect a single gateway to multiple workspaces using an OAuth token file. Each workspace gets its own bot token, resolves dynamically. If you manage clients or teams across multiple Slack workspaces, this is a time saver. Third, Telegram webhook mode. The old way Hermes connected to Telegram was polling, constantly checking for new messages. Webhook mode flips that. Telegram pushes messages to Hermes instead, faster, cleaner, better for production deployments. And there is also a new Exa search backend. You now have an alternative to Firecrawl and DuckDuckGo for web search inside your agent, more options, more flexibility depending on what your workflow actually needs. Now, I want to talk about something for anyone coming from Open Claude. Open Claude was a popular open source agent that a lot of people were using before Hermes became a serious option. If you've been running Open Claude, switching has historically meant manually migrating settings, memories, API keys, a whole pain. Hermes 0.6 expanded its Open Claude migration guide significantly. It now covers sessions, cron jobs, and memory. The migration tool lets you do a dry run first so you can see exactly what would be moved before you commit to anything. And during first-time setup, Hermes automatically detects if you have Open Claude installed and offers to migrate before you even configure anything. That is a smooth path for anyone sitting on the fence about switching. Let me give you the community numbers on this release because they tell you something about where this project is heading. Hermes Agent was at 18,200 GitHub stars around the time of this launch. Version 0.6 shipped 95 pull requests in just two days. The community around this tool is building fast. So, what does version 0.6 actually mean for your workflows right now? Multiple agents running in parallel, your existing tools plugged in via MCP, automatic failover if a provider goes down, Slack working across all your workspaces at once. And if you've been waiting for Hermes to mature enough to be worth your time, that time is now. To get started, you run one command. Curl the install script, works on Linux, macOS, and WSL2 on Windows, no prerequisites except Git. Hermes handles Python, Node, dependencies, everything. Then run Hermes setup to configure your model provider and connect your messaging platforms. And if you want profiles, Hermes profile create gives you a new isolated agent in seconds. That is it. That is the whole setup. If you are looking to dive deeper into AI tools and actually implement them in your work, I recommend AI Profit Boardroom, over 2,000 people learning how to use AI effectively. Everyone shares real experiences, what is working, what is not, which tools are worth your time, which ones to skip. No hype, just solid information and practical guidance from people doing the work. It has helped me stay on top of updates like this one and figure out how to actually apply them. Link in description if you want to check it out. And if you want the full process, SOPs, and 100 plus AI use cases like this one, join the AI Success Lab. Links in the comments and description. You will get all the video notes from there plus access to our community of 58,000 members who are crushing it with AI. Hermes Agent 0.6 is out now. The documentation is live at hermesagent.nousresearch.com. Go check it out.