Hermes Agent adds memory, browser tooling

This is a meaningful infrastructure upgrade, not just a feature bump: Hermes is getting the reliability primitives an always-on agent needs before memory and browser automation matter in practice.

• –Pluggable memory providers make the system less opinionated and easier to adapt to different backends, from vector stores to custom databases.
• –Same-provider credential pools and automatic failover are the kind of boring reliability work that matters when an agent runs 24/7 against rate limits and flaky APIs.
• –The new Camofox browser backend strengthens web automation, but also signals the project is leaning harder into stealthy browser execution and scraping workflows.
• –Loop hardening, inline diffs, and security filtering all reduce the “agent drift” problem that usually makes long-running autonomous systems fragile.
• –ACP client-provided MCP server support is a strong ecosystem move for IDE users, since it lets Hermes inherit tools from editor integrations instead of duplicating them.