Hermes Agent 0.22.4, released by Nous Research on October 21, 2026, is worth installing if your team uses the WhatsApp Dashboard or installs plugins often. The patch fixes a blocked WhatsApp re-pairing path, an incorrect approval-mode indicator, and an empty dependency prompt during plugin installation.
Hermes AgentAI agentAn AI program that performs work steps by itself, for example reading a message, drafting a reply, and recording the result.Open the glossary is an open-source AI agent that can perform tasks, use tools, and connect to channels such as WhatsApp. Unlike a basic chatbot, an agent can complete a sequence of actions. Its permission state and channel connection must therefore be accurate and visible.
What changed in Hermes Agent 0.22.4?
The official Nous Research release notes describe 0.22.4 as a patch release with six fixes. It is available for the CLI/installer, Microsoft Store, Docker, and Hermes Cloud. The Desktop app installed from an .exe or .dmg does not receive a new bundle in this release.
| Change | Previous problem | Daily impact |
|---|---|---|
| WhatsApp re-pairing | An old creds.json made the Dashboard treat the account as connected | An admin can request a new QR without moving folders by hand |
| Approval mode | The chip could show smart while the active profile used off | The permission state now follows the active profile and connection |
| Plugins with no dependencies | An empty consent prompt appeared and non-interactive installs failed | The plugin enables directly when it installs no packages |
| Suggestion pills | MCPMCPA standard that lets an AI program use your tools and data under clear permissions.Open the glossary suggestions appeared after unrelated keyword matches | The composer no longer pushes an unwanted setup step |
Why does the WhatsApp re-pairing fix matter?
PR #142439 from October 21, 2026 explains the root cause. After WhatsApp removed a linked device, its credentials file could remain on disk. The old pairing action read that file as an active account, so it did not offer a new QR. Recovery required an admin to move the session directory manually.
Version 0.22.4 adds a confirmed Re-pair with QR action. Hermes moves the old session to a timestamped backup directory, creates a fresh session, and starts the existing QR flow. The process refuses a reset when the gateway or another pairing process holds the lock. This reduces the risk of two processes writing credentials at the same time.
For a business owner or marketer, the visible benefit is simple. An admin can recover a disconnected WhatsApp channel without opening the server and finding a session folder. For a developer, the useful parts are the backup, process lock, PID checks, and race-condition tests. The PR reports 29 focused tests passing on Windows. However, the author did not test pairing with a live WhatsApp account. Your own channel test remains necessary.
What feels better in daily use?
Approval mode controls how freely the agent can execute actions. PR #142565 from October 21, 2026 found that the status chip always started with smart. Its mode request ran before the gateway WebSocket opened, failed silently, and did not run again. The interface could therefore show smart while the profile was set to off.
The patch waits until the gateway is open and synchronizes again after a reconnect. This is not only a visual correction. An operator who checks permissions in the status bar now gets a more consistent signal before assigning a sensitive task.
Plugin installation is also more direct. PR #142569 from October 21, 2026 records that a plugin with an empty dependency list still entered the consent step. In a non-interactive install, the plugin could be installed but left disabled. Version 0.22.4 asks for consent only when the plugin will install packages into the shared environment.
Should you upgrade now or wait?
- Upgrade now if WhatsApp has logged out, the Dashboard cannot show a new QR, or your team automates plugin installation.
- Use a maintenance window if approval mode is part of your operational control process.
- You can wait if you only use Desktop from an .exe or .dmg, because the release notes say that route has no new bundle yet.
Before the upgrade, back up the configuration and sessions. Record each profile's approval mode. Then test one incoming and one outgoing message on a non-production channel. After the upgrade, check the gateway connection, approval status, active plugins, and QR flow. Keep the old session backup until message delivery is stable.
If you are still evaluating the platform, read our Hermes Agent and OpenClaw comparison. To select a first workflow, use these Hermes Agent examples for business.
Hermes Agent 0.22.4 questions
Is 0.22.4 a major release?
No. Nous Research calls it a patch release. It fixes recovery and usability paths instead of changing the main architecture.
Does re-pairing delete the old WhatsApp session?
Not directly. The implementation moves the old session to a timestamped backup directory before it creates a new session.
Do .exe and .dmg users get this Desktop update?
Not through a new bundle yet. The release notes say those installer routes must wait for the next bundled release.
Do the official tests guarantee production WhatsApp safety?
No. The PR reports automated tests, but it did not pair a live WhatsApp account. Test a non-production channel first.
Operational conclusion
Hermes Agent 0.22.4 does not add a large feature. It fixes three points that can waste operator time: WhatsApp pairing, permission status, and plugin installation. If any of them is part of your workflow, make a backup, upgrade, and run a smoke test on the same day.
