The human story in Hermes Agent this week is not just that web search got another backend. It is that a contributor made search easier to use, then the project had to decide how much identity a free tool path should expose.
The convenience patch
Commit e0e25717, authored by Matt Harris and merged June 10, rewired Hermes' Parallel provider around two routes. Without PARALLEL_API_KEY, web_search and web_extract use Parallel's hosted Search MCP. With a key, the same provider uses Parallel v1 REST search and extract.
The patch is unusually explicit about user experience. It stops prompting users to configure web just because web.backend is unset, registers web tools with the free MCP as a backstop, and adds tests for anonymous headers, Streamable HTTP responses, web fetch ordering, keyed REST limits, and display labels.
The policy correction
The follow-up commit 0a5762c7, authored by Teknium, did not remove the feature. It changed the free MCP client identity from a Hermes-branded value to a generic mcp-web-client value, saying project policy forbids third-party usage attribution without explicit user opt-in.
That is a small code change with a large product lesson. Removing setup can create a new kind of default: a service sees traffic, a tool path has attribution, and a project has to decide whether that attribution belongs to the user, the tool vendor, or nobody by default.
Why it matters
The maintainer question is constructive and factual: when a hosted MCP makes agent tools work immediately, what should the client reveal before the user has chosen that provider? Harris' patch answers the ergonomics problem; Teknium's patch answers part of the consent problem.
Neither commit proves a finished web-search policy for every agent. Together, they show an agent runtime growing up in public: a contributor lowers the barrier to useful tools, and maintainers tighten the boundary so convenience does not quietly become attribution.