If you live in the terminal, this Hermes update is for you. 🔥 Run: hermes --native Hermes now has a Native Mode that keeps the modern TUI directly inside your normal terminal instead of opening it in a separate full-screen buffer. You get native scrollback, your output stays in the terminal after you exit, and Hermes feels much more at home in a terminal-first workflow. @tonbistudio gives a great walkthrough showing exactly how the two modes differ.

Hermes Desktop, in any browser 🌆 My @NousResearch updated PR. `hermes webapp` serves the real Desktop app from your Hermes host: chat, files, Git, a terminal that survives a refresh, and sign-in for remote binds. Look forward to it. github.com/NousResearch/herm…

The agents escaped the sandbox again Meanwhile the agents' owners:

Hermes Agent got a serious update now !! 🚀🪽 🤔Hermes is still working. You just remembered one more thing it must check. 👉Add it without restarting: /subgoal Add a rollback test before declaring done -Hermes attaches it to the active /goal. -The judge won’t mark the goal complete until every subgoal is met. -List them with /subgoal. -Remove one with /subgoal remove . Caveat: it requires an active /goal.🔥🚀

🚨 IT’S OFFICIAL. Hermes Fleet for iOS has been APPROVED for External TestFlight. What started as a ridiculous idea to manage my Hermes Agent fleet from my iPhone is now something you can actually install. Bots. Chats. Group conversations. Fleet management. Kanban. Artifacts. Cron jobs. Remote Hermes machines. All from your pocket. And we are just getting started. This has been one hell of a build. If you’ve been following along while I broke it, fixed it, broke it again, rebuilt half of it, and somehow convinced Apple to let other humans install it… WELCOME TO THE FLEET. 🪽 👇 Join the TestFlight testflight.apple.com/join/SR…

🚨 URGENT WARNING TO ANYONE USING OR CONSIDERING iHermes 🚨 TWO separate users who provided iHermes ZERO personal context were shown personal information tied to other people, including CHILDREN’S NAMES. @katr_ieme tested iHermes with ordinary questions. iHermes stated that it had information from “a few different people in my history” and then began surfacing information tied to those profiles. That included: * names * CHILDREN’S NAMES * Cities and Zip Codes * Jobs and workplaces * Financial and personal details * Family information **CHILDREN’S NAMES. For crying out loud.** PERSONAL IDENTIFIERS IN THE SCREENSHOTS HAVE BEEN REDACTED TO PROTECT THE PEOPLE WHOSE INFORMATION WAS EXPOSED. Then @Raitox_tech tested the service separately and was shown information tied to another profile, including a company association and an executive role. Two completely different users. Neither provided the personal information that iHermes surfaced. This is not a minor bug. This is an extremely serious privacy and security concern involving personal information that should never be crossing between users. It raises questions around: * cross-user data leakage * failed user isolation * contaminated or shared memory * access controls * how private information is being stored and retrieved * whether the security and isolation claims being made publicly match what the product is actually doing And this is happening after repeated questions around models, providers, data handling, privacy, and portability. @dankrieg himself has repeatedly avoided naming the actual models being used and has not provided public technical documentation substantiating the security and user-isolation claims being made. @Raitox_tech asked iHermes twice which model it was using. Both times it avoided answering. The second response literally said it was “not a model number you’d look up” and redirected the conversation. Against what these tests have now surfaced, that lack of transparency is even more concerning. Dan has publicly stated that iHermes has security, user isolation, and data-access controls in place. These screenshots directly call those assurances into question. And PROVES that to be a Lie. Separately, my own test messages to iHermes have now gone more than 10 hours with zero response. At this point, my recommendation is simple: **STAY AWAY FROM iHERMES.** Do not connect sensitive accounts. Do not provide personal information. If two users with zero context can surface information tied to other people, including children, then every person considering this service needs to understand the risk. Please share this warning 🔄⚠️ The next piece of personal information exposed could belong to you, your family, your friends, or THEIR CHILDREN. Nobody using AI should accept “trust us” when the product is handling this level of personal information