This has always been possible with Vaultwarden. I don't understand why people get so excited for things like this when it isn't anything new.
Does your agent need to sign in? With 1Password for Agents, agents can sign in and complete tasks securely without seeing or storing passwords, secrets, or credentials.
The 1Password for Agents platform is building with companies @Muse, @Bot, @AnthropicAI @claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_Use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way 🎉
My wife and I loved Six Flags Fright Fest around Halloween when we were teenagers.
Our kids have zero interest. We have tried to get them to go for three years. They also have zero interest in Disney parks.
I even talked to their friends' parents. I thought a group trip might change their minds. Only two kids wanted to go.
I wonder if my father ever felt like the world had changed so much that he couldn't recognize it?
I am bad at social media. I am also bad at knowing what is worth posting.
I had Grok Bot and Dot talking to my Hermes agents within hours of their release. The integrations were not perfect. They worked well enough for what I needed. Hermes has also managed my NetBox and vCenter for months.
I thought those connections were obvious. I thought nobody would care how I made them work. Then I saw posts about the same things get a lot of views.
So now I ask: what am I doing today that will be a hot topic three months from now?
A few things on my list:
1. I am giving my agents more access to Hyper-V and Windows Sandbox.
2. Hermes builds VM templates in Hyper-V and vCenter. Sysprep was a pain. It works now. Hermes deploys its own disposable VMs the same way it deploys Docker containers.
3. I used clean-room reverse engineering to rebuild tools that help with reverse engineering. That made every other project easier. I have five clean-room projects running now.
4. Hermes makes very good offline copies of websites for those projects. Very good copies.
5. I am building a library of reverse-engineered components to reuse as building blocks in my own projects.
I could keep going.
None of this felt worth a post. My default thought is, "Everyone already does this. Why read about me doing it?"
Then I keep seeing posts do well that I would have skipped for that exact reason.
I need to recalibrate what I call obvious.
Which one should I write up first?
Chat history is evidence, not my long-term system of record. My agent does the work; durable records preserve what I’ll need next week.
My Obsidian vault holds knowledge, decisions, and receipts I can open later. GBrain makes that knowledge searchable, it’s a rebuildable retrieval layer, not the source of truth. Honcho adds conversation recall and user modeling to Hermes alongside its built-in memory.
Before asking me to repeat myself, search the relevant records and check their sources. After meaningful work, changes, verification, or decisions queue a concise Daily Log receipt.
I posted a while back that I run three primary Hermes agents. One installed on Linux, one in Docker, and one installed on Windows. That is not one bot running three times.
A Hermes profile is not a skin. It is a separate Hermes config with its own skills, memory, sessions, and profile-scoped settings. Provider or tool auth can still be shared across profiles when you reuse the same OAuth or CLI login. Do not read "profile" as "unique credentials forever."
When several local profiles sit behind one Hermes process on the same host, each turn loads that profile's own Hermes state. Think profile isolation for agent config and settings. That is not an OS permission boundary. The shared Hermes gateway on that host only serves local profiles.
So I still split the work by where I want the agent to live. Host shell work stays on the Linux install. Container work stays in Docker. Desktop work stays on Windows.
I posted a while back that I run three primary Hermes agents. One installed on Linux, one in Docker, and one installed on Windows. That is not one bot running three times.
A Hermes profile is not a skin. It is a separate Hermes config with its own skills, memory, sessions, and profile-scoped settings. Provider or tool auth can still be shared across profiles when you reuse the same OAuth or CLI login. Do not read "profile" as "unique credentials forever."
When several local profiles sit behind one Hermes process on the same host, each turn loads that profile's own Hermes state. Think profile isolation for agent config and settings. That is not an OS permission boundary. The shared Hermes gateway on that host only serves local profiles. It does not join a Linux install, a Docker install, and a Windows install into one security model.
So I still split the work by where I want the agent to live. Host shell work stays on the Linux install. Container work stays in Docker. Desktop work stays on Windows. Those OS or container boundaries are separate from Hermes profile isolation. Putting an agent in Docker does not make it a safe sandbox by itself.
Before you invent another profile, ask what Hermes state it needs that the others do not. If two local profiles own the same config and the same job, ask whether you actually need both.
I have been using my Dot as a voice interface for my Hermes agents. Today my Dot started refusing some requests. The requests were to ask Hermes to do something. I was setting up a new server so it was doing a lot of things using elevated privileges until Dot decided I wasn't allowed to do that. I kept trying to work with Dot but finally I just gave up and started typing to Hermes directly. Hermes refused too, it had never done that before. After some digging I found that Dot had told Hermes to enforce the same restrictions Dot has. It took me an hour to rip all that out of Hermes. It sucks because Dot is the best voice experience I have used. However, telling my other agents to enforce security limitations that I did not ask for and did not approve is unacceptable.
My Hermes kanban cards spend more time blocked and stopped than they do running and I can't seem to find a way to prevent that. Does anyone else have this problem? Does someone have a solution?
I had an OpenAI usage reset that expired tonight. With about 20 minutes left, I was about to use it when the power went out. It stayed out for five hours.
I didn’t have a laptop with me, and that’s when I discovered I couldn’t use a reset or even check my usage on mobile, either in the app or through the website. So the reset expired unused.
Moral of the story: don’t wait until the day your reset expires to use it.
I am looking forward to this coming to @NousResearch's portal.
Jev by @typesafeai is now on OpenRouter, in beta.
Jev is a System One model. Instead of generating text, it takes your app's state plus a typed question and returns a typed decision with a probability attached. There is no JSON prompting, parsing layer, and nothing to validate against.
Oh I like this!
My Hermes Agent has a newspaper for me now. 🗞️🚀
The Hermes Agent Times: four pages covering my day, my agents’ work, ideas worth exploring, and life beyond the screen.
🚀Next: a morning printout and an Obsidian archive connecting each day’s ideas.
Would you read a newspaper made by your own agent?
# Give below prompt to your Hermes agent👇 @Teknium @NousResearch
I am not so sure about this. This seems like one of those things that after it has gone horribly wrong someone says "well it seemed like a good idea at the time"
I discovered this morning that my work account has Astra and I have been playing with it for the last two hours. I also am testing it via my Azure account. I have been trying workflows in the lab that 5.6 Sol can't do. Astra has so far completed them all successfully. In fact despite my best efforts I can't seem to find something it can't do. I had it set up a completely new vnet in Azure with all our standards for routing and security. Everything, and there is a lot. It takes us days to do it even with parts of it being automated. It did it all in a little over an hour. All I gave it was our documentation which is outdated. It figured out the problems with the documentation and created updated documentation for me to approve. All of our validation tests are still running but so far nothing has been flagged. The validations are going to take longer than it did to build it all. 5.6 Sol could not get past the first step because it requires navigating the GUI of an internally developed system that frankly looks like it was designed by a drunken orangutan. Astra had no problem with it. I have it doing a test new site deployment in the lab now which is another thing 5.6 Sol can't do. It is already past the point that 5.6 Sol fails at. I have not added any new skills or special tooling. It has exactly the same setup as Sol. I am honestly stunned. I can't let it out of the lab yet but when security and compliance approve deployment it will have a massive impact.
Here is a clean version of the eve-ng Hermes skill that I use. It is what I used when using Hermes to create an eve-ng lab from a screenshot. github.com/TheCodeOfDave/her…















