Nous released Hermes Agent v0.7.0 with an extensible memory plugin system, rotating credential pools, Camofox browser support, and inline diff previews. The update pushes the framework closer to production use, so teams can test the new failure handling and interface split before adopting it.
You can jump straight into the full v0.7.0 release notes, skim the new memory provider list, compare it with the separate credential pool flow, and inspect the browser automation docs to see how Camofox sits next to Browserbase, Browser Use, and local Chrome.
The core architectural change is boring in the best way. According to Teknium, Hermes is starting to push subsystems behind defined interfaces so the core code can stay smaller while third-party implementations expand around it.
The first subsystem to move is memory. The release notes describe an ABC-based plugin system with built-in memory still available by default, and the Memory Providers docs show the current external options:
That matters because Hermes now separates two kinds of persistence that often get blurred together. The docs say the built-in MEMORY.md and USER.md stay in place, while an external provider can add cross-session retrieval, background prefetch, and sync back from conversations into a dedicated memory backend.
Hermes now supports multiple credentials for the same provider, not just a single key plus a fallback vendor. In Teknium's example, that can mean a personal account and a corporate account cycling automatically for one provider.
The Credential Pools docs fill in the mechanics:
round_robin, least_used, fill_first, and randomThe release notes also say pool state survives smart-routing and fallback transitions, which is the kind of detail you only add after seeing real traffic behave badly.
Hermes already had browser tooling. v0.7.0 adds a new local backend aimed at stealthier automation.
The release notes call it a Camofox anti-detection browser backend with persistent sessions, VNC URL discovery for visual debugging, SSRF-bypass controls for local backends, and auto-install support through hermes tools. The browser automation docs add the implementation detail: Camofox is a self-hosted Node.js server wrapping Camoufox, a Firefox fork with fingerprint spoofing.
That puts Hermes in an odd but increasingly common place for open agent frameworks: not just calling models and tools, but shipping opinions about how to survive hostile websites.
The CLI change is easy to grasp. File writes and patches now render inline diffs in the tool feed, and Teknium says the view is on by default but can be disabled.
The denser part of the release is everything grouped under hardening in the official notes. Nous says the gateway got fixes for race conditions, photo-media delivery, flood control, stuck sessions, approval routing, and what it calls compression death spirals. The same release also adds secret-pattern scanning across browser URLs and model responses, with blocking for exfiltration attempts that use URL encoding, base64, or prompt-injection tricks.
For teams running Hermes as more than a local toy, that cluster is probably the real headline. Memory plugins are the flashy part. Reliability work is what turns a fast-moving repo into something you can leave running.
The same v0.7.0 release notes tuck in two more upgrades that did not make the social posts. The API server now streams tool progress in real time and accepts X-Hermes-Session-Id headers so sessions can persist across requests in a shared SessionDB.
Nous also added client-provided MCP server support for editor integrations. In the release notes, that specifically means VS Code, Zed, and JetBrains can register their own MCP servers so Hermes can pick them up as additional tools.
That is a useful tell about where Hermes is heading. Teknium's repo-growth post said the project was already the third-fastest-growing GitHub repository that week, and the v0.7.0 changes read less like a feature dump than a framework trying to become a stable runtime for long-lived agents.