Hermes Camofox is the official Hermes Agent plugin that lets your agent browse the web with Camoufox, a Firefox fork built to avoid bot detection, running on your own machine with no cloud service. It used to be built into Hermes itself; now it’s a separate plugin in the Hermes Official Plugins collection from Nous Research. The newest change (28 October 2026) lets Hermes’ password vault fill your saved logins straight into the Camofox tab, without the password ever entering the chat. That change is on the main branch but not yet in a tagged release (the latest is v0.22.5 from 23 October), so you may need the newest build to get it. Below I cover what Camofox is, how to install it, how to keep your logins between sessions, how cookie import works, and the safety rules worth knowing, all from the plugin’s own README. I’ve also added my video on Hermes browsing the web as you.
Key takeaways
- Install:
hermes plugins install camofox, then run the Camofox server yourself. - Browses locally with a fingerprint-spoofing Firefox fork. No cloud browser.
- Saved logins from the vault now fill on the Camofox tab (plugin v1.1.0).
- Keep logins between sessions with
managed_persistence: true. - Want browser agents working for your business? Claim a free strategy session.
What is Hermes Camofox?
Camofox is two pieces working together. camofox-browser is a small self-hosted Node.js server that wraps Camoufox, a version of Firefox with fingerprint spoofing built into its C++ code. The Hermes Camofox plugin talks to that server over its REST API, so your agent gets a real, local, anti-detection browser.
Why that matters: lots of websites block or challenge obvious automation. A browser that looks like a normal person’s Firefox gets through far more often. And because it runs on your machine, you don’t pay for or depend on a cloud browser service.
The plugin gives Hermes the same browser tools its skills already use, in a toolset called camofox: navigate, snapshot, click, type, scroll, back, press, get images, vision and console. With a Camofox API key set, it also adds browser_import_cookies.
What’s new: saved logins on the Camofox tab
On 28 October 2026, Nous added vault fill to the plugin. Hermes has a built-in tool called browser_vault that uses your saved logins, cards, addresses and one-time codes on a page “without the secrets ever entering the conversation.” Until now it only worked on Chromium-style browsers. Now it works on the Camofox tab too.
How it stays safe, according to the README:
- It only fills a tab the agent already opened with
browser_navigate. It never opens one itself. - It checks the page’s exact origin matches the saved login before filling.
- It only sends the password when your Camofox server address is local (loopback) or HTTPS.
- A filled password shows as
«redacted-vault-secret»in the agent’s page snapshot.
This needs a Hermes version with the new browser page backend support. On older versions, the agent has to type credentials with browser_type instead.
Want browser agents set up and working for you? Inside the AI Profit Boardroom you get the Agent OS — Hermes, OpenClaw, OpenCode, Claude and Codex in one place — plus step-by-step Hermes training and four live coaching calls a week.
Want a plan for your business first? Claim your free strategy session.
Join the AI Profit Boardroom →Claim Your Free SEO Strategy Session →
How to install Hermes Camofox
Hermes doesn’t install or start the Camofox server for you, so there are two parts. First, the plugin:
hermes plugins install camofoxThe installer asks for CAMOFOX_URL, the address of your Camofox server. Then run the server itself. The simplest way is native Node, which also works on Windows:
git clone https://github.com/jo-inc/camofox-browser
cd camofox-browser
npm install && npm start
# -> http://localhost:9377The first run downloads Camoufox, which is several hundred MB. There’s also a one-line shortcut, npx @askjo/camofox-browser, and a Docker image:
docker run -d -p 9377:9377 -e CAMOFOX_PORT=9377 ghcr.io/jo-inc/camofox-browser:latestFinally, check everything with hermes camofox setup (saves the URL and an optional API key to your profile) and hermes camofox status (shows whether the server is reachable). The tools appear once the URL is set and the camofox toolset is on in hermes tools.
Easier option: ask your agent, “Install the Camofox plugin, start a local Camofox server, and check hermes camofox status.”
Already used Camofox? Nothing breaks
If you used Camofox when it was built into Hermes, you don’t need to change anything. The README says CAMOFOX_URL, the other CAMOFOX_* settings and every browser.camofox config key work as before, and your saved logins carry over.
The browser docs add that existing Camofox setups are migrated automatically on update: the plugin gets installed and the core browser toolset is switched off in that profile.
How to keep your logins between sessions
By default each session gets a random Camofox identity, so cookies and logins disappear on restart. To keep them, turn on persistence in ~/.hermes/config.yaml:
browser:
camofox:
managed_persistence: trueEach Hermes profile then gets its own Camofox browser profile. One catch: cookies are only written to disk at a checkpoint. A graceful shutdown of the Camofox server saves them; force-killing it (kill -9, Task Manager) loses any logins that weren’t saved yet.
The README’s trick for sites that need a real sign-in:
- Start Camofox in desktop mode, so a visible browser window opens.
- Ask Hermes to open the site, then sign in yourself in that window.
- Save the session (a checkpoint, or a graceful shutdown).
- Switch back to headless mode and restart. Hermes now uses your logged-in session without a window.
Want this set up for you instead of doing it yourself? Claim your free strategy session →
Import cookies instead of logging in
Already logged in on your normal browser? Export the site’s cookies as a cookies.txt file with a browser extension, put it in ~/.camofox/cookies, and ask Hermes something like: “Import my LinkedIn cookies from linkedin.txt, then open my feed.”
This needs CAMOFOX_API_KEY set in Hermes and on the server. The limits are sensible: files must sit in that cookies folder, they’re capped at 5 MB and 500 cookies, and cookie values are never written to the logs.
Safety settings worth knowing
- Blocked URLs: navigation refuses URLs containing a Hermes secret, cloud-metadata addresses, and anything on your
security.website_blocklist. - Safer JavaScript:
browser.restrict_evaluate: truerefuses console commands that touch cookies, storage or network calls. - Watch typed passwords: the README warns that Camoufox shows typed field values in page snapshots. A password the agent or you type by hand appears there, which is exactly why vault fill is the better way to log in.
- Docker users: if pages are served from your own machine, turn on
rewrite_loopback_urlsso the browser inside the container can reach them.
Camofox vs Hermes’ built-in browser
Hermes’ own browser tools drive Chromium. Camofox is the option for sites that fight automation, or when you want a fully local stealth browser. A few differences from the README:
- The Camofox snapshot is a single view, with no compact/full switch.
browser_visionalways answers through your auxiliary vision model.browser_consoleruns JavaScript but can’t capture console logs.
You can run both: a profile that adds the plugin after updating keeps browser_exec alongside it.
My verdict
If your agent keeps getting blocked, or you want it working inside sites you’re logged in to, this is the plugin to set up. It’s local, free, MIT-licensed, and now safe for logins thanks to vault fill. Install it, turn on persistence, sign in once in desktop mode, and Hermes Camofox handles the rest.
About Julian Goldie
I’m Julian Goldie — founder of Goldie Agency and the AI Profit Boardroom. I test new AI agents almost every day for 432K+ YouTube subscribers and run Hermes, OpenClaw, OpenCode, Claude and Codex side by side in my own Agent OS. Claim your free strategy session or join the AI Profit Boardroom.
Want another angle? Read the AI Profit Boardroom guide to Hermes Camofox.
FAQ: hermes camofox
What is Hermes Camofox?
Hermes Camofox is an official Hermes Agent plugin that drives a self-hosted Camofox server, which wraps Camoufox, a Firefox fork with fingerprint spoofing. It gives Hermes a local anti-detection browser with no cloud dependency.
How do I install Camofox in Hermes?
Run hermes plugins install camofox, start the Camofox server yourself (npm start in the camofox-browser repo, npx @askjo/camofox-browser, or the Docker image), then check it with hermes camofox status.
Is Camoufox the same as Camofox?
Camoufox is the Firefox fork with fingerprint spoofing. Camofox (camofox-browser) is the Node.js server that wraps it, and the Hermes plugin is also called Camofox.
Can Hermes Camofox use my saved passwords?
Yes. Since 28 October 2026 the browser_vault tool can fill saved logins on the Camofox tab, with exact-origin checks, and only when the Camofox server is local or HTTPS. The password never enters the chat.
How do I keep logins between sessions?
Set browser.camofox.managed_persistence: true. Each Hermes profile then gets its own persistent Camofox profile. Shut the server down gracefully so cookies are saved.
Does Hermes install the Camofox server for me?
No. Hermes never installs or starts the Camofox server. You run it yourself and point Hermes at it with CAMOFOX_URL.
Ready to put Hermes to work in your business? Join the AI Profit Boardroom for the Agent OS, setup training and daily updates.
Or claim your free strategy session and we’ll map out your setup.
Starting from zero? Get the free AI course and community.
Join the AI Profit Boardroom →Claim Your Free SEO Strategy Session →Get the FREE AI Course + Community →
Related reading
Last updated October 2026. This page is a living guide to hermes camofox — the facts here move fast and it is updated as they do.
