Hermes Camofox is the official Camofox browser plugin for Hermes Agent, built by Nous Research, that lets your agent browse the web through a local anti-detection browser instead of plain Chromium. You install it with one command, point it at a Camofox server you run yourself, and Hermes gets ten browser tools that drive a fingerprint-spoofing Firefox. As of 28 October 2026, it can also fill your saved logins on the Camofox tab.
📺 Watch: Hermes Agent Can Now Browse the Web as YOU
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
What is Hermes Camofox?
Camofox (built on Camoufox) is a self-hosted Node.js server from the jo-inc/camofox-browser project. Per the plugin README, it wraps Camoufox, "a Firefox fork with C++ fingerprint spoofing". Sites that block obvious bots see a browser that looks like a normal person's Firefox.
The Hermes plugin talks to that server over its REST API. That means two things:
- It runs locally. No cloud browser vendor, no extra account. The README calls it "a local anti-detection browser and no cloud dependency".
- It's a plugin, not core. Camofox used to be built into Hermes core. On 22 October 2026, Nous Research removed the built-in browser tools and the bundled Camofox from hermes-agent (commit 68500d9f), and Camofox moved into the hermes-official-plugins repo.
The repo describes itself as the official plugins for Hermes Agent, "built and maintained by Nous Research". Camofox sits there next to Spotify, Home Assistant, ElevenLabs Music and others. Don't mix this up with Hermes Labs (hermes-labs.ai), which is a separate, independent company.
Want Hermes set up inside a full agent system with browser tools, profiles and skills already wired? The AI Profit Boardroom ($69/mo) gives you the Agent OS, a 30-day AI agent roadmap, daily tutorials as new tools ship, weekly coaching calls and the prompt library.
What the Camofox plugin gives your agent
The plugin registers its tools in a toolset called camofox. These are the same tool names skills already call, so existing skills keep working:
- browser_navigate, browser_back and browser_scroll to move around a site.
- browser_snapshot to read the page as an accessibility tree.
- browser_click, browser_type and browser_press to act on the page.
- browser_get_images and browser_vision to look at what's on screen.
- browser_console to evaluate JavaScript.
- browser_import_cookies, offered only when a Camofox API key is set.
The README lists three differences from Hermes' other browser backends. The snapshot has no compact or full switch. Vision always answers through the auxiliary vision model, with no numbered-label overlay. And the console evaluates JavaScript but can't capture console logs, because the Camofox REST API doesn't expose them.
📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office
How to install Hermes Camofox
There are two parts: the Camofox server, and the Hermes plugin. Hermes never installs or starts the server for you.
Step 1: run the Camofox server
The native Node path is the README's first choice, and it works on Windows too. Clone jo-inc/camofox-browser from GitHub, then run npm install and npm start. The server comes up on localhost port 9377. The shorthand is npx @askjo/camofox-browser.
The first run downloads Camoufox, which is hundreds of MB. A GET request to the /health endpoint should report ok as true. If you prefer Docker, the image is ghcr.io/jo-inc/camofox-browser:latest, published on port 9377.
Step 2: install the plugin
Run hermes plugins install camofox to pull it from the plugin catalog. You can also install it straight from the repo with hermes plugins install NousResearch/hermes-official-plugins#camofox. The installer asks for your CAMOFOX_URL.
Step 3: check it
Two commands come with the plugin:
- hermes camofox setup saves CAMOFOX_URL, plus an optional CAMOFOX_API_KEY, to the profile's .env file.
- hermes camofox status shows the configured URL, identity mode, whether the server is reachable, and the VNC address.
The tools appear once CAMOFOX_URL is set and the camofox toolset is switched on in hermes tools. If you run more than one Hermes profile, each one is set up on its own. My guide on Hermes multiple profiles covers how profiles split config and logins.
Already used Camofox with Hermes before the move? The Hermes docs say existing setups are migrated automatically on update: the plugin is installed and the core browser toolset is turned off in that profile. Your CAMOFOX variables and browser.camofox config keys keep working.
📺 Watch: Hermes Bot Mode DESTROYS Grok Bot? (FREE!)
Hermes Camofox config keys that matter
Here are the settings from the plugin's configuration reference and README, in one place.
| Setting | Default | What it does |
|---|---|---|
| CAMOFOX_URL (.env) | None | Camofox server URL. Required. |
| CAMOFOX_API_KEY (.env) | None | Sent as a bearer token to a server started with an API key. Unlocks cookie import. |
| browser.camofox.managed_persistence | Off | Gives each Hermes profile its own Camofox identity so logins survive restarts. |
| browser.command_timeout | 30 | Per-request timeout in seconds. Floor of 5; navigation allows 60. |
| browser.snapshot_threshold | 15000 | Long snapshots are cut at a line boundary and the full tree is saved to file. |
| browser.restrict_evaluate | false | Refuses console expressions that touch cookies, storage or network calls. |
| browser.camofox.cookies_dir | ~/.camofox/cookies | Where cookie files for import must live. |
| interactive.mode (server) | off | Set on the Camofox server: off (headless), desktop, novnc or auto. |
Keeping logins between sessions
By default, each session gets a random Camofox identity, so cookies don't survive a restart. Turn on managed_persistence and Hermes sends a fixed userId per profile instead.
One catch from the README: live cookies sit in the open browser context until Camofox checkpoints them to disk. That happens on a POST to /stop (which needs CAMOFOX_ADMIN_KEY) or a graceful Node shutdown. Force-killing Node drops any login that was never checkpointed.
Cookie import
With an API key set on both sides, browser_import_cookies loads a Netscape-format cookies.txt file into the current Camofox user. Files must sit inside the cookies folder, are capped at 5 MB and 500 cookies, and cookie values are never logged.
Need help mapping this onto your own business tasks? Book a free AI strategy session and we'll map out which browser jobs are worth handing to an agent.
New on 28 October 2026: browser_vault fills logins on Camofox
Hermes has a password vault tool called browser_vault. It fills a saved login into a page without the password ever entering the model's context. Until this week it couldn't reach Camofox, because Camofox has no CDP endpoint for the vault's supervisor to talk to.
On 28 October 2026, Nous Research shipped the fix in three commits:
- In hermes-agent, commit 0a93a234: "fill saved logins on Camofox pages through a browser page backend seam".
- In hermes-official-plugins, commit 6f7d49b5: "browser_vault fills saved logins on the Camofox tab", plus a same-day fix so vault fills ignore environment proxies.
- Back in hermes-agent, commit 6f553435 pins the catalog's camofox plugin to that new version.
Here's how it works, per the plugin README and the Hermes vault docs:
- The vault reads the tab's origin and inspects the form, then writes the password through Camofox's evaluate endpoint.
- The same exact-origin checks apply as on a CDP browser. A login saved for one site won't fill on another.
- It only fills a tab that browser_navigate already opened. It never opens one itself.
- It only sends the password when CAMOFOX_URL is loopback or HTTPS.
These commits landed after v0.22.5 (23 October), the latest tagged release at the time of writing, so you need a Hermes core with the new seam. If you store logins in a password manager, my guide on Hermes and 1Password shows how the vault reads from it.
When to use Camofox instead of the default browser
Hermes' default browser is browser_exec, which drives a packaged Chromium with Python over CDP. The Hermes docs also list cloud options: Browser Use Cloud, Browserbase, or your own running Chrome.
Pick Camofox when:
- Sites flag or block your agent's normal Chromium.
- You want anti-detection without paying a cloud browser vendor.
- You want the browser and its cookies to stay on your own machine.
Stick with browser_exec when you need CDP features like the dialog supervisor, which the Hermes docs say doesn't apply to Camofox. A profile that sets up the plugin after the update keeps browser_exec alongside it, so you can have both.
The Agent OS guide shows how a browser agent fits into a bigger setup with scheduled jobs and other agents. For how different agents score on real tasks, see Goldie Bench.
Want the full system with Hermes, browser automation and the rest of the Agent OS ready to go? Join the AI Profit Boardroom and use the setup prompts from day one.
Hermes Camofox FAQ
Is Camofox the same as Camoufox?
No. Camoufox is the Firefox fork with fingerprint spoofing. Camofox is the Node.js server from jo-inc that wraps Camoufox and exposes a REST API. The Hermes plugin talks to Camofox, which drives Camoufox.
Does Hermes install the Camofox server for me?
No. The README says Hermes never installs or starts the Camofox server. You run it with npm or Docker, then give Hermes the URL with hermes camofox setup.
Do my old Camofox settings still work?
Yes. Per the plugin README, CAMOFOX_URL, the other CAMOFOX variables and every browser.camofox config key work as before. With managed_persistence on, the plugin sends the same profile-scoped userId core used, so saved logins carry over.
Can browser_vault fill passwords on Camofox?
Yes, since the 28 October 2026 commits, on a Hermes core with the browser page backend seam. It fills only on an exact origin match, only on a tab Hermes already opened, and only when CAMOFOX_URL is loopback or HTTPS.
Ready to put Hermes to work on real tasks for your business? Book a free AI strategy session and get a plan for which jobs to automate first. Prefer to talk it through live? Grab a free strategy session here.
