My Hermes webapp verdict: it's the most useful thing in the v0.22.6 release for anyone who runs Hermes on one machine and works from several, and it scores 8.1 out of 10 on my card.
It landed in Hermes Agent v0.22.6 on 2 November 2026, and its job is to hand the complete native workspace to any browser tab, straight from the gateway.
Below is the scorecard, the strengths, the limits, who should switch it on, who shouldn't, and the final call.
Want my team to look at where agents fit your business before you commit? Book a free SEO strategy session.
What Was Reviewed
This verdict rates the feature against the official documentation: the Desktop docs section on using the workspace from a browser, the Webapp configuration reference, the CLI reference for hermes webapp and the v0.22.6 release notes.
Ratings are editorial judgement from what those pages say the feature does.
Where the docs set a hard number, such as a port, a timeout or a file limit, the number is quoted exactly.
The release notes themselves call this feature "undocumented here on purpose" and promise full curated notes with v0.23.0.
That's why documentation scores a 7: the reference pages are detailed, but the release announcement points you elsewhere.
The Scorecard
| Criterion | Rating | Reason from the docs |
|---|---|---|
| Setup effort | 9/10 | Three commands: enable, restart the gateway, run hermes webapp. |
| Feature parity with Desktop | 8/10 | Sessions, profiles, Capabilities, Messaging, Artifacts, jobs, files, Git, previews and terminal all come across; a short native-only list stays behind. |
| Local sign-in design | 9/10 | One-use links valid for 60 seconds, kept per tab, with OS-specific protection on Linux, Windows and macOS. |
| Remote access options | 8/10 | A Web Access pane with This network and My own URL, both behind Nous sign-in. |
| Safety defaults | 9/10 | Off by default, loopback by default, and a non-loopback host or public URL forces a sign-in provider. |
| Plain-HTTP experience | 6/10 | Mic, clipboard reading, notifications and the bot screen viewer switch off away from the host. |
| Plugin support | 8/10 | Desktop plugins load in the tab, and installs are pinned to the commit you reviewed. |
| Diagnostics | 9/10 | --status names the exact reason the gateway can't serve it. |
| Documentation | 7/10 | The Desktop and config docs are thorough; the release notes hold detail back until v0.23.0. |
| Overall | 8.1/10 | Average of the nine criteria above. |
Strength: It Really Is The Desktop, Not A Lite Version
The gateway serves the same workspace the native app shows.
Chats run on that gateway, which also serves the CLI, the native app and messaging, so there's one conversation and one queue across every surface.
Even display preferences are shared through one ui-preferences.json per computer, and browser tabs pick up changes when they regain focus or within about ten seconds.
That's a stronger design than a separate web client with its own state.
Strength: Safe By Default
The webapp: block ships with enabled: false and host: 127.0.0.1.
webapp:
enabled: false # true: the gateway serves the Webapp
host: 127.0.0.1 # 127.0.0.1, ::1 or localhost; or 0.0.0.0 / :: for other machines (dashboard sign-in required)
port: 9120 # fixed, so the browser's address stays the same across gateway restarts
public_url: "" # the https:// address a reverse proxy or tunnel serves the Webapp at (sign-in required)Change the host to 0.0.0.0 or ::, or set public_url, and the gateway demands a dashboard sign-in provider.
Without one, it serves native clients only and refuses the Webapp, rather than serving it open.
Odd values, including other loopback addresses like 127.0.0.2, keep it off too.
That fail-closed behaviour is why safety defaults earn a 9.
Strength: Sign-In Built Around Your OS User
Local sign-in gets a 9 because it's designed around who can reach the link, not just how long it lasts.
The link from hermes webapp works once and only within 60 seconds.
The CLI reference adds that only your own OS user can get a link, because the gateway answers the command over its private control socket.
On Linux the gateway checks that the browser's connection belongs to your OS user.
Windows keeps the link out of reach by passing it only through the launcher's command line, hidden from other standard accounts.
On macOS, the BSDs and illumos, the command writes the link into a page only your user can read and opens that, so the launcher sees just a path.
Once used, the tab keeps its sign-in through reloads and gateway restarts, while a fresh tab or bare URL shows instructions instead of access.
New Window, profile windows and session pop-outs each get a one-use link of their own.
The only soft spot is the printed link from --no-open: until it's used, it signs a browser in as you, so it has to stay private.
Strength: Web Access Makes Remote Use A Button
The native app's Settings → Web Access pane handles the fiddly parts.
One press of Start covers the build, the Nous sign-in registration for the address, the saved settings and the gateway restart.
It waits politely if a chat is running, showing Restart needed until the chat ends.
It uses its own Nous sign-in client and leaves dashboard.public_url alone, so a dashboard you publish separately keeps working.
🔥 Want the Agent OS that puts Hermes on every screen, done for you? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members comparing their agent setups. → Join the AI Profit Boardroom
Limit: Plain HTTP Costs You Features
The lowest score on the card goes to the LAN option's browser experience.
On a plain-HTTP address that isn't loopback, browsers block the bot screen viewer, the microphone, reading the clipboard and system notifications.
That hits dictation, live voice, the remote wake word, terminal paste and pasting an image.
The fix exists, either HTTPS via webapp.public_url or an SSH tunnel to 127.0.0.1, but it's extra work the This network option doesn't do for you.
The docs also note This network traffic isn't encrypted and is only for networks you trust.
Limit: A Login Is Full Host Access
This isn't a flaw so much as the nature of the feature, and the docs say it plainly.
Per the warning box, whoever signs in can execute commands under the Hermes OS account, work with its files and Git repos, and read the secrets that account holds.
So the Webapp has no role for a junior team member with limited rights.
Anyone you let in gets everything the host account has.
Limit: Some Features Stay Native
The Electron app keeps a handful of features to itself: its updater, global shortcuts, always-on-top overlays, external-terminal launch and inspecting OS windows.
Browser uploads cap at 16 MiB per file, and Save Image for cross-origin URLs needs CORS, with a 25 MiB limit and a 30-second deadline.
Older chats from before the gateway owned sessions need hermes sessions adopt before you can continue them in the browser.
None of these are deal-breakers, but they keep feature parity at 8 rather than 10.
How It Compares With The Web Dashboard
| Point | Hermes Webapp | Hermes Web Dashboard |
|---|---|---|
| Purpose | Work: chats, files, Git, terminal, artifacts | Admin: config, keys, sessions, logs, analytics |
| Command | hermes webapp | hermes dashboard |
| Default port | 9120 | 9119 |
| Served by | The gateway's own listener | The dashboard server |
| Non-loopback bind | Needs a dashboard sign-in provider | Engages the auth gate |
The dashboard docs describe it as a browser UI for managing your installation, and its Chat tab embeds the TUI.
The verdict on the overlap is simple: run both if you want, they don't replace each other.
Plugins In The Browser Tab
Desktop plugins load in the Webapp from the host's desktop-plugins folder, whichever profile the tab is on.
Installs from Capabilities → Plugins → Install are held to the commit the dialog showed, and if the branch moved after you looked, nothing installs until you review the new one.
A browser-requested clone refuses symbolic links and anything over 64 MB.
That earns plugin support an 8, held back only because a plugin's ctx.files access doesn't work in a browser.
For which plugins deserve a slot, see the best Hermes Agent plugins ranking.
Diagnostics And Recovery
hermes webapp --status reports whether the gateway serves the Webapp and at which address.
When it can't, it names the cause: a taken port, a required sign-in with no provider, or an unreadable webapp/session-token file.
--sign-out closes every browser connection at once, and behind the sign-in gate it forces every dashboard login to sign in again.
Clear messages like these are rare, and they lift the diagnostics score.
Recovery is just as plain: fix the cause, run hermes gateway restart, and the gateway reads the new settings on start.
An unbuilt bundle needs no restart at all, since hermes webapp builds it and the running gateway serves it straight away.
📞 Weighing which agent tools are worth your team's time? Book a free SEO strategy session and my team will go through your stack with you. → Claim your free strategy session
Who Should Turn It On, And Who Should Wait
Turn it on
- Solo operators who run Hermes on a desktop and want it on a laptop or phone.
- Anyone with a headless Hermes host, since desktop plugins appear there even where native Desktop never runs.
- People already running Tailscale, a tunnel or a reverse proxy, who can use My own URL straight away.
- Multi-profile users, who can open a profile directly with
hermes -p work webapp.
Wait for now
- Anyone who'd need to share the login with people they wouldn't give the host account to.
- Installer-based Desktop users who want the Web Access pane today, since the release notes say installer builds get v0.22.6 with the next bundled release.
- Anyone whose only remote option would be forwarding the port from a home router, which the docs rule out.
Final Verdict
8.1 out of 10.
Seven of the nine criteria score 8 or higher, and none falls below 6.
For a feature that shipped in a patch release with its notes held back, that's an unusually complete first version.
The Webapp does what it promises: the real Desktop workspace in a browser, off by default, locked to loopback by default, and fail-closed when you open it up.
The weak spot is plain HTTP on a LAN, which trades away voice, clipboard and notifications, so go straight to HTTPS or an SSH tunnel if you'll use it away from the host.
Run hermes config set webapp.enabled true to switch it on, give the gateway a restart, then launch it with hermes webapp.
If you want the full Agent OS around it, with trainings and live calls, join the AI Profit Boardroom.
Also On Our Network
- 🌐 The six-step setup for the Hermes Webapp, from config to remote sign-in
- 🌐 Whether a small business should run its Hermes agent from a browser
- 🌐 Five copy-paste prompts to run your Agent OS through the Hermes Webapp
- 🌐 Which AI models to run in Hermes Webapp sessions, by real GoldieBench scores
- 🌐 The complete Hermes Webapp guide on the AI Profit Boardroom blog
FAQ: Hermes Webapp Verdict
What score does the Hermes Webapp get?
8.1 out of 10, the average of nine criteria rated from the official docs. Plain-HTTP use on a LAN is its weakest area at 6 out of 10.
Is the Hermes Webapp a replacement for the Web Dashboard?
No. The Webapp is the working Desktop workspace on port 9120, while the dashboard is an admin panel on port 9119. They do different jobs.
Is it safe to leave the Webapp on?
On the default loopback host, only your machine can reach it and every tab needs a one-use sign-in link. Opening it to other machines requires a sign-in provider.
Who gets the most from it?
Solo operators with Hermes on one machine, headless-host users, and people who already run Tailscale, a tunnel or a reverse proxy.
What is the biggest limitation?
On a plain-HTTP LAN address, browsers turn off the microphone, clipboard reading, notifications and the bot screen viewer. HTTPS or an SSH tunnel keeps them.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Switch it on, keep it on loopback or HTTPS, and if you want my team to judge where it fits your stack, book a free strategy session and bring your questions on the Hermes webapp.
