OpenClaw and Hermes agree on what an agent is. They disagree on what controls it.

Two open-source agent runtimes, OpenClaw and Hermes Agent, are competing for control of the agent layer. OpenClaw, backed by OpenAI, Nvidia, and Microsoft, focuses on broad channel connectivity and enterprise governance, while Hermes Agent from Nous Research emphasizes persistent memory and self-improvement. Hermes has overtaken OpenClaw in OpenRouter token rankings and offers a migration command to import OpenClaw settings, signaling a land grab in the agent runtime space.

The race for the agent runtime isn't about models. It's about who controls the layer that keeps an agent alive, gives it memory, and decides what it can touch. Two open projects defined that layer in 2026. OpenClaw, built around a broad gateway connecting agents to dozens of messaging channels, drew OpenAI, Nvidia, and Microsoft into its orbit. Hermes Agent, from Nous Research, built around persistent memory that learns a developer's codebase and refines itself over time — and overtook OpenClaw in OpenRouter's daily token rankings in May. They agree on what an agent harness is. They disagree on which part matters most. OpenClaw went enterprise via platform vendors. Nvidia wrapped it in NemoClaw at GTC in March, sandboxing each agent and enforcing policy from outside the agent's reach. Microsoft made it native to Windows execution containers at Build in June, shipping Scout — an enterprise agent with an Entra identity, wired into Teams, Outlook, and SharePoint. Breadth got distribution; the platform vendors added the controls. Hermes built depth via memory. Released February 25 under MIT license, Hermes keeps a layered memory across sessions, develops new skills after hard tasks, and refines them with use. It builds a profile of the developer it works with — so each session starts with more context than the last. By late June, it sat at 22 trillion tokens on OpenRouter's app rankings, first by total usage. Hermes also ships a migration command. hermes claw migrate imports an OpenClaw user's settings, memories, skills, and keys in a single step. That's not a feature — it's a land grab. The analogy holds: this is managed cloud vs. self-managed infrastructure. OpenClaw is the managed path — platform-governed, vendor-controlled, increasingly integrated into enterprise tooling. Hermes is the self-hosted path — you own the infrastructure, you own the memory, you own the switching cost. "Memory, more than channel reach, is becoming the durable form of lock-in." That's the crux. An agent that's learned a year of a developer's habits, conventions, and decisions is far stickier than one that merely connects to many applications. NemoClaw already runs Hermes agents alongside OpenClaw agents — the governance layer is being built beneath both projects, not betting on one. The security audit that flagged 341 malicious skills in ClawHub's marketplace and tens of thousands of exposed instances earlier this year tells you something too: distribution without governance is a liability. The platform vendors showed up precisely to fix that. hermes claw migrate already works — the projects are converging faster than the star counts suggest.Source: OpenClaw and Hermes: Two Architectures Fighting for the Agent Control Layer https://thenewstack.io/author/janakiram/ — Janakiram MSV, The New Stack ✏️ Drafted with KewBot AI , edited and approved by Drew.