Hermes update · dropped Aug 11, 2026

The One-Script Engine

Hermes just cut browser agents to half price

Hermes AI just changed browser agents.

Nous Research dropped an update a few hours ago that takes twelve separate browser tools and replaces all of them with one.

In their own tests, it cut token use by 48 to 66 percent.

Same accuracy. Same results. Roughly half the cost.

By the end, you'll know exactly how it works, how to turn it on, and the one setup where it doesn't work at all.

navigate click type scroll press …7 more ONE tool it writes a script 66% fewer tokens same accuracy
Straight from Nous Research — read it yourself ↓
§1 01 · What actually changed

Hermes had twelve browser tools.

One to navigate. One to click. One to type. One to scroll. And eight more.

browser_navigate browser_snapshot browser_click browser_type browser_scroll browser_press browser_back browser_get_images browser_vision browser_console browser_cdp browser_dialog twelve tools · twelve instruction manuals · carried in EVERY request

The real twelve — these are the actual tool names from the Hermes docs.

§2 02 · Why that was a problem

Every request carried all twelve manuals.

Even to click one button, the AI hauled the instruction manual for every tool. Every single time.

"Click one button" the whole job manual ×12 manual ×12 manual ×12 manual ×12 Wasted tokens before the agent even does anything
§3 03 · But it gets worse

Click. Report. Think. Repeat forever.

Every single action was its own round trip back to the model.

CLICK STOP + REPORTback to the model THINK…the meter runs NEXT ACTIONone click at a time every action = a full lap

What you're watching: the classic twelve-tool loop — one tool call per action, a full stop after every step. Recreated at reading pace from the real Hermes tool names; this is exactly the loop the update kills.

§4 04 · The supermarket test

Phoning a friend before every aisle.

"Can I walk to aisle three?" Yes. "Can I pick up the milk?" Yes. You'd lose your mind — and burn a fortune in calls.

The old shop aisle 3? the milk? trolley? checkout? 📞 The new shop THE LIST ✓ aisle 3 ✓ milk → trolley ✓ checkout 🛒 one trip · zero phone calls
§5 05 · The new way

Browser Use mode: one plan, written once, run start to finish.

Instead of twelve tools, the agent gets one — and writes one script that handles the whole job.

Tweet 1 · the announcement

Nous says it plainly: twelve became one

This is the official drop — twelve browser tools replaced by a single one, driven by Browser Use's CLI 3.0. The agent writes a script instead of firing a tool call per click, and their own tests measured a 48–66% token cut with no accuracy drop.

Old way 12 tools · 50k–64k tokens
  • Twelve tool manuals carried in every request
  • One tool call per click, type, and scroll
  • Full stop + report after every action
  • The model re-thinks between every step
  • Slow, and the meter runs the whole time
New way 1 tool · low-20k tokens
  • One tool, one instruction manual
  • The agent writes one script for the whole job
  • Navigate, click, type, scrape — start to finish
  • No permission-asking between steps
  • Same accuracy, roughly half the cost

What you're watching: a real Hermes session on this machine — one plain-English ask, the agent drives Browser Use CLI 3.0, and live Hacker News headlines come back. Real commands, real output, replayed at reading pace.

§6 06 · The framework

The One-Script Engine.

Understand this and you understand where all AI agents are heading.

i.

One Tool

Twelve instruction manuals shrink to one. The AI stops paying to carry what it isn't using.

ii.

One Script

The AI writes the full set of instructions up front — like your friend writing the whole shopping list.

iii.

One Trip

Navigate, click, type, scrape, done. No phone calls home between steps.

ONE TOOL1 manual, not 12 ONE SCRIPTthe whole plan, up front ONE TRIPstart → finish, no stops
§7 07 · The numbers

The same job, for a third to half of yesterday's cost.

With Opus 4.8 driving the browser, tasks that burned 50,000–64,000 tokens dropped into the low 20,000s.

BEFORE · 12 tools 64k 50k AFTER · Browser Use mode low 20k 4866% token cut · 0% accuracy drop

Nous Research's own test numbers, posted this morning — same accuracy, roughly a third to half the tokens.

§8 08 · Straight from the lead engineer

"I told you we'd get you 60% less token spend."

Tweet 2 · the receipt

Teknium, cofounder and lead engineer on Hermes Agent

He promised the 60% cut before it shipped — and this is him calling it delivered, crediting Browser Use and their new CLI 3.0 backend for driving the browser.

§9 09 · Where the savings come from

Two leaks, both sealed.

The tool manual shrank from a whole stack to one — and the agent now drives the browser with code, so the whole conversation gets shorter.

Leak 1 · the manualsa stack of schemas → just one Leak 2 · the chatteractions → one block of code A way, way shorter conversation
§10 10 · Why tokens are your ceiling

The meter just started running 60% slower.

Cheaper agents, longer runs, bigger jobs, more runs per day — the token cost was the ceiling, and Nous just raised it.

the meter · 60% slower site 1checked ✓ site 2checked ✓ site 3checked ✓ site 4checked ✓ site 5checked ✓ Your daily competitor check now costs about half of what it did last week
§11 Put Hermes to work in your business

Get the One-Script Engine running inside your Agent OS.

Hermes is wired directly into our Agent Operating System — the same system where you plug in your Claude, your OpenClaw, your Free Claude Code, all sharing one memory.

The Agent OS zip file — Hermes browser automation pre-wired, step by step
A 30-day roadmap — set the whole system up piece by piece
Daily updates — as we improve it, including this new Browser Use mode
Four coaching calls every week — bring your own Hermes setup, get it fixed live
3,800+ business owners — plenty of them running Hermes right now
Get the Agent OS → Inside the AI Profit Boardroom · aiprofitboardroom.com
Set up in an afternoon · used in 38 countries · new tools added the week they ship
Thinking it? "Doesn't running an Agent OS burn a fortune in tokens?"

No — that's the biggest myth about it. The everyday 90% runs on free local models and free APIs, and for the frontier work it drives the CLIs you already pay for — your Claude subscription already includes the Claude CLI.

It's a layer on top of what you already own, not a new meter. And this exact update just cut the browser half of the bill again — plus the Boardroom has full token-efficiency tutorials inside.

§12 11 · How to turn it on

It's probably already on.

If the Browser Use CLI can run on your machine, this mode is now the default — Hermes checks, and quietly falls back to the old twelve tools if it can't.

# force it on — one line in ~/.hermes/config.yaml browser: backend: "browser-use"
# turn it off — one command /browser use off
Tweet 3 · the setup line

Nous posted the switch themselves

One config line to force it on. That's the whole setup — and if you'd rather keep the old tools, it's one command the other way.

What you're watching: the real update run on this machine — hermes update pulls the release, the new browser_exec tool lands, and the config line locks it on. Real commands, real output.

Thinking it? "So I need another subscription for browser-use.com?"

No. The new mode drives your own local browser for free — the Browser Use CLI is open source.

Their cloud browsers are an optional extra, and every other setup (Browserbase, your local Chrome, the built-in browser) keeps working with its existing credentials.

§13 12 · The first belief to drop

"This sounds like coding. It isn't — for you."

Wrong: "The agent writes Python scripts now — that means I need to be a coder to use this."

Right: The agent writes the code, runs it, and reports back. You type a plain sentence — "go to this website and fill in the contact form." If you can write a text message, you can run this.

You: a plain sentence"fill in the contact form" The AI writes the Python navigate → type → click → submit runs it itself · you never see it Done ✓form filled, report back
§14 13 · It works with your setup

Not locked to one browser.

Local Chrome, Browserbase, Browser Use cloud — the new mode sits on top and drives whichever browser you've already picked.

Browser Use mode one driver · CLI 3.0 Your local Chromefree Browserbasecloud Browser Use cloudcloud Firecrawlcloud
§15 14 · The one exception

The catch: Camofox.

The privacy-focused local browser has no CDP endpoint for the new harness to attach to — Camofox setups automatically keep the old twelve tools. Nothing's broken; it's just not supported there yet.

🦊 Camofoxlocal anti-detection browser no CDP endpoint to attach to Keeps the 12 toolsautomatic fallback · nothing breaks
Thinking it? "I flipped the setting and nothing changed."

Check if you're on Camofox — that's almost certainly why. And one honest note: because this mode runs real code on your machine, Hermes only offers it in sessions with terminal access. Locked-down setups (like a messaging-only surface) keep the standard tools — a safety choice, and the right one.

§16 15 · The clever detail in the docs

Public sites go cloud. Private stuff stays home.

Hybrid routing: normal websites use your cloud browser, but anything on your own machine or home network gets a local browser automatically — the cloud provider never even sees it.

Your agentone conversation github.com → cloud localhost:3000 → local ☁ Cloud browserpublic websites 🏠 Local browseryour dashboard · your LAN · never leaves home
§17 16 · The boring jobs it takes off your plate

The point was never the technology.

A shop owner's supplier-price watch every morning. A freelancer's hour of directory scraping — done while you're on a client call.

What you're watching: the Browser Use CLI 3.0 for real on this machine — it opens a live site, reads the page state with numbered elements the agent can act on, and closes clean. This is the exact harness Hermes now drives.

Wrong: "AI agents are too expensive to run every day. That's for big companies with big budgets."

Right: That was fair last week. But when a task drops from 50,000–64,000 tokens to the low 20,000s overnight, the math on "run this every single day" changes completely. Jobs that didn't make sense last Monday make sense now.

§18 17 · "But browser agents are just demos"

Fewer moving parts. Fewer ways to get lost.

Wrong: "Browser agents look good in a video but they're not reliable enough for real work."

Right: Nous measured no accuracy drop — and the whole approach got simpler. One tool instead of twelve means fewer round trips, and fewer chances for the agent to lose the thread. Still check its work. Still start small. But "this stuff never works" gets more outdated every month.

1 2 3 4 5 …12 12 handoffs · 12 chances to drop the thread One script · one thread measured: zero accuracy drop
Don't take my word for it

Members post their wins every day — agency owners, ecom founders, course creators, solo operators across 38 countries. Real businesses, real numbers, in their own words.

Read the 158-page wins doc →
§19 18 · Zoom out

The agents were always capable. They were just run expensively.

"A dozen schemas per click was never a capability problem, it was a token tax nobody totaled up until now."

— @tabor_bachelor, replying to the Nous Research announcement, Aug 11, 2026

Ask permission at every step the expensive way · fading out Plan the whole job up front every major agent tool is heading here — Hermes got there first, in public, with numbers
§20 19 · What to actually do

Three steps. All simple.

1.Already run Hermes?

Update it and check whether Browser Use mode is active — if the CLI is available, it probably already is. Run one small browser task and watch how much faster it feels.

2.Don't run Hermes yet?

Genuinely good week to start. It's free, it's open source from Nous Research, and browser automation just became one of its strongest features. Give it one boring job you do every week.

3.The one that matters most:

Pick a real, repeating, annoying task from your business — not a test, not a toy. Hand it to the agent. The moment you watch it complete a real job, something clicks about what's now possible.

§21 Your move

Get the One-Script Engine built for you.

This update handed everyone a browser agent that costs roughly half as much to run as it did yesterday. The question is whether you'll actually use it — and inside the AI Profit Boardroom, we've built the setup path for exactly this.

The Agent OS zip file — Hermes plugs in alongside Claude, OpenClaw, and Free Claude Code, all sharing one memory
Workflows for browser tasks — plus research agents, SEO agents, even video and avatar tools
The 30-day roadmap — video tutorials and daily updates as new versions ship, including this Browser Use mode
Four weekly coaching calls — bring your Hermes browser setup, get it fixed live
Daily step-by-step tutorials — putting agents to work for leads and customers
3,800+ business owners — many running Hermes daily, plus a member map to find people near you. There's always someone online.
Get the Agent OS → Inside the AI Profit Boardroom · aiprofitboardroom.com
Link in the description · used in 38 countries · new tools added the week they ship
§22 20 · One last thought

It shipped quietly, on a Tuesday, as a config setting.

Twelve tools became one.

Token costs dropped by more than half.

Accuracy stayed the same.

That's what progress in AI looks like right now — not always a flashy new model, but the running costs of useful work quietly falling through the floor.

The gap between people who use this stuff and people who watch videos about it grows a little wider every week.

Pick one boring job this week. Hand it to an agent. Start there.

"Twelve tools became one. The meter runs 60% slower. Your move."