Optimize browser console evaluations by 180x

What changed

Hermes Agent now routes browser tool calls through a persistent Chrome DevTools Protocol connection. The change replaces per-call session initialization with a single long-lived link to Chrome.

Latency for console evaluations dropped from multiple seconds to milliseconds. Internal benchmarks show an average 180x speedup on repeated browser interactions.

Why it matters

Vibe Builders who delegate web tasks to Hermes gain reliable sub-second feedback loops inside the same agent that already handles Telegram, Discord, and Slack. The update removes the main friction point in browser automation without requiring extra services or paid tiers.

It pressures hosted agent platforms that still spin up fresh browser instances on every request. The bet is that persistent local connections will become the default for any self-hosted agent that touches the web regularly.

How to use it

Pull the latest code with the built-in /update command inside an active Hermes session. Confirm the new Browser Use backend is active by running a test console evaluation through the local web dashboard.

No extra configuration files or environment variables are required. The persistent connection starts automatically when the agent launches with browser tools enabled.

Watch for

Confirm the bet if repeated browser tasks stay under 200 ms even after hours of uptime. Watch for memory leaks or Chrome crashes that would force a restart of the entire agent. The next expected move is similar persistent connections for other remote execution backends such as Docker or Modal.