Hermes Camofox earns an 8 out of 10 from me: it's the strongest way to give Hermes Agent a browser that blends in, as long as you're willing to run the server yourself.
It's the official Camofox plugin, maintained by Nous Research in the hermes-official-plugins repo, and it drives Camoufox, a Firefox fork with fingerprint spoofing at the C++ level.
Every rating on this page is my editorial call from the plugin README, the camofox-browser README, the Hermes docs and the commit history.
No benchmarks were run for this review.
If you'd rather have my team judge whether a browser agent fits your business, book a free SEO strategy session.
The Hermes Camofox verdict in one paragraph
Use it if sites keep turning away your agent's Chromium and you want the fix running locally.
Skip it if you want zero setup, or if you need password fills on Camofox from a tagged release today.
The plugin is well documented, the migration from core is painless, and the safety rules around passwords are careful.
The cost is operational: you own a Node server, its uptime, and the moment its cookies get saved to disk.
Scorecard: Hermes Camofox rated on nine criteria
| Criterion | Score /10 | Why, from the docs |
|---|---|---|
| Blending in on the real web | 9 | Camoufox spoofs hardware, WebGL, audio, screen and WebRTC signals before page JavaScript sees them. |
| Local control | 9 | The README promises a local anti-detection browser with no cloud dependency. |
| Setup effort | 6 | Hermes never installs or starts the server; you run Node or Docker yourself. |
| Tool coverage | 8 | Ten browser tools plus cookie import, under the same names skills already call. |
| Login persistence | 7 | Works with managed_persistence, but cookies only hit disk at a checkpoint. |
| Password handling | 8 | Vault fills are origin-bound and loopback or HTTPS only, but the fix is untagged. |
| Debugging | 6 | No console log capture and a single snapshot view. |
| Migration from core | 9 | Old CAMOFOX_* vars and browser.camofox.* keys work unchanged. |
| Documentation | 9 | The README spells out defaults, limits and exactly when logins reach disk. |
The average lands at 7.9, which I round to the 8 in the headline.
Strength: the browser runs on your machine
The camofox-browser README pitches the problem bluntly: Playwright gets blocked, headless Chrome gets fingerprinted, and stealth plugins become the fingerprint.
Camofox answers with Camoufox, patched at the C++ level, and wraps it in a REST API built for agents.
Nothing leaves for a third-party browser vendor, which is the deciding factor for anyone who doesn't want a provider's browser seeing their pages.
Idle memory sits around 40MB per the same README, thanks to lazy launch and idle shutdown.
The snapshots it returns are accessibility trees with stable element refs like e1 and e2, which the README says are about 90% smaller than raw HTML.
Smaller snapshots mean the model reads less per page, which matters on long runs through many pages.
Long pages get cut at the browser.snapshot_threshold of 15000, and the full tree is saved to a file the agent can page through.
That design is the main reason blending in and local control both score a 9.
🔥 Want this browser stack wired into a full agent system instead of a weekend project? 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 who share what works. → Join the AI Profit Boardroom
Strength: existing skills keep working
The plugin registers ten tools that cover navigation, page reads, clicks, typing, scrolling, key presses, images, vision and JavaScript, from browser_navigate through to browser_console.
Those are the tool names skills already call, so a skill written against the old browser tools doesn't need rewriting.
Settings carry over too: CAMOFOX_URL, the other CAMOFOX_* variables and every browser.camofox.* key behave as before.
Profiles that used Camofox in core get the plugin installed automatically on update, per the Hermes browser docs.
That counts for a lot after core deleted its own browser_* tools on 22 October 2026 in commit 68500d9f, leaving browser_exec as the only core browser driver.
Strength: password fills that respect the site
When the vault fill works, it's tightly fenced.
It only fills a tab that browser_navigate already opened, it requires an exact origin match, and the password travels only to a Camofox address on loopback or HTTPS.
A filled value shows as «redacted-vault-secret» in the snapshot.
The Hermes credential vault docs confirm the same exact-origin checks run on Camofox as on a CDP browser.
The vault itself brings more than passwords: it can generate 2FA codes from a saved authenticator key and pick up logins from 1Password or Bitwarden when their command-line tools are signed in.
Card fills always ask for approval first, and unattended sessions such as cron jobs are refused.
For an agent browser that blends in, that approval rule is exactly the guard rail I want to see.
Strength: cookie import with sensible fences
Cookie import is the fastest route into a site you're already signed into elsewhere.
You export a Netscape-format cookies.txt, drop it in ~/.camofox/cookies, and the agent calls browser_import_cookies.
The tool only appears when CAMOFOX_API_KEY is set, and the server must run with the same key.
Absolute paths and ../ are refused, each file may hold at most 500 cookies within 5 MB, and the logs never record a cookie value.
Off by default and fenced like that, it's a feature I'd rate well above average for an agent browser.
Limit: you run and babysit the server
Setup is two parts, and only one of them is Hermes.
The first Camoufox download is around 300MB, per the camofox-browser README.
Docker users also have to think about loopback rewriting, because inside a container 127.0.0.1 is the container.
The camofox-browser server also sends anonymized crash and hang reports to GitHub Issues unless you set CAMOFOX_CRASH_REPORT_ENABLED=false, which is one more default to review.
Each Hermes profile needs its own CAMOFOX_URL, so multi-profile setups repeat the work.
That's why setup scores a 6, not lower: the commands are short, but they're on you.
Limit: a thinner toolbox than browser_exec
The plugin README lists three gaps against Hermes' other browser backends.
browser_snapshothas no compact or full switch.browser_visionroutes every question to the auxiliary vision model and draws no numbered labels on the page.browser_consoleevaluates JavaScript but can't capture console logs.
There's a safety setting worth flipping here: browser.restrict_evaluate: true refuses console expressions that name cookies, storage or network calls.
It defaults to false, which is the one default in the plugin I'd change on every install.
And because Camofox has no CDP endpoint, browser_cdp and browser_dialog, which the Hermes browser docs tie to a CDP endpoint, aren't part of the Camofox toolset.
Limit: logins live in memory until a checkpoint
Ending a Hermes session doesn't close the Camofox session, and live cookies stay in the open browser context.
They reach disk on POST /stop with an admin key, or on a graceful SIGINT or SIGTERM.
Force-kill Node and any login that wasn't checkpointed is gone.
The headed login routine helps: sign in once in a visible desktop window, checkpoint, then switch interactive.mode back to off for headless reuse.
It's documented clearly, which is why persistence still scores a 7, but it's a trap for anyone who restarts servers carelessly.
Limit: the vault fix isn't in a tagged release
The Camofox vault fill landed on 28 October 2026 in hermes-agent commit 0a93a234 and plugin commit 6f7d49b5.
The latest tagged Hermes release is v0.22.5, published 23 October 2026, so it doesn't carry the fix.
On an older core the plugin skips the registration, and the README says to type credentials with browser_type, which prints the value into snapshots.
That gap is why password handling scores an 8, not a 9.
How Camofox compares with Hermes' other browser options
| Option | Where it runs | Best for |
|---|---|---|
| Local Chromium (default) | Your machine, headless | Everyday interactive pages, no setup |
| Cloud browsers | Nous subscription, Browserbase, Browser Use, Firecrawl | No local server to maintain |
| Lightpanda | Your machine | Text-first browsing on small machines |
| Your own browser | Your running Chrome, Brave, Chromium or Edge | Working inside your live session |
| Camofox plugin | Your Camofox server | Sites that block automated browsers |
The first four come straight from the Hermes browser docs; Camofox is the only one built specifically to look like a regular person's browser.
Who should use Hermes Camofox
- Operators whose agents keep getting blocked or served different pages on Chromium.
- Teams that want logins and cookies kept on their own hardware.
- Anyone who already ran Camofox in core and wants the same setup after the move.
- Agencies that split clients across Hermes profiles and want each one in its own browser identity.
- Builders comfortable running a main-branch core who want vault fills now.
Who shouldn't
- People who only need to read public pages, where
web_searchorweb_extractis faster and cheaper per the Hermes docs. - Anyone who needs raw CDP commands or native dialog handling.
- Teams that want password fills on Camofox but run tagged releases only.
- Anyone with no one to restart the server when it stops.
If you land in this group, stay on the default local Chromium and revisit Camofox once the vault fix ships in a tagged release.
The switch is cheap later, because a profile that sets up the plugin keeps browser_exec alongside it.
📞 Weighing a browser agent against the rest of your marketing plan? Book a free SEO strategy session and my team will tell you where an agent fits and where your time is better spent. → Book the free session
Final verdict on Hermes Camofox
Hermes Camofox is the best browser choice in Hermes when blending in matters more than convenience.
The engineering is careful, the docs are honest about the sharp edges, and moving from core costs you nothing.
Hold back one point for the server you have to run and another for the untagged vault fix.
Once a tagged release carries the 28 October commits, password handling climbs to a 9 and the overall score with it.
Set it up, turn on managed_persistence, and shut Node down gracefully every time.
Want the Agent OS and trainings that put this browser to work? Get into the AI Profit Boardroom.
Also On Our Network
- 🌐 The six-step Camofox setup, from npm start to persistent logins
- 🌐 Whether a small business should run Camofox, with three real use cases
- 🌐 Five copy-paste prompts that get your agent running Camofox
- 🌐 Which AI models to run behind Camofox, with live GoldieBench scores
- 🌐 The complete Hermes Camofox guide on the AI Profit Boardroom blog
FAQ: Hermes Camofox Verdict
What score does Hermes Camofox get?
8 out of 10. It scores highest on blending in, local control, migration and documentation, and lowest on setup effort and debugging.
Is Hermes Camofox better than the default Chromium browser?
For sites that block automated browsers, yes. For public pages that load fine, the default Chromium is simpler and needs no server.
What's the biggest weakness?
You run the Camofox server yourself, and logins only reach disk at a checkpoint or a graceful shutdown, so a force-kill loses them.
Were these ratings based on benchmarks?
No. They're editorial ratings drawn from the plugin README, the camofox-browser README, the Hermes docs and the commit history.
Does Camofox support raw CDP commands?
No. Camofox has no CDP endpoint, so browser_cdp and browser_dialog aren't part of its toolset.
📺 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
Rated 8 out of 10, so run it where Chromium gets blocked, keep passwords in the vault, and if you want help deciding, book a free SEO strategy session or join the AI Profit Boardroom and set up Hermes Camofox.
