Skip to content
AI Primer
release

Hermes Agent adds /background command and OpenClaw migration path

Hermes Agent added a /background command and a migration path from OpenClaw. Use it to lower setup friction for parallel task runs and to trial Hermes without rebuilding your whole stack.

3 min read
Hermes Agent adds /background command and OpenClaw migration path
Hermes Agent adds /background command and OpenClaw migration path

TL;DR

  • Hermes Agent now has a /background command for “run a prompt in the background,” according to Teknium's command post, which lowers friction for parallel agent runs inside the CLI.
  • Hermes also added an OpenClaw migration path: the migration note says setup can import an existing OpenClaw configuration instead of forcing a rebuild from scratch.
  • Early adoption appears to be rising quickly. A Nous-shared usage chart shows Hermes Agent usage on OpenRouter climbing toward the 14B mark over the last 30 days, while Nous is positioning it broadly with its “for everyone” post.
  • Practitioner reports suggest Hermes is already being used for longer-running, multi-step workflows, with one user report saying it started a project, recorded a clip, and sent it to Telegram without the user expecting the full chain.

What shipped in Hermes Agent?

The concrete product change is the new /background command. In Teknium’s post, the built-in help text describes it as “Run a prompt in the background,” with usage shown as /background <prompt>. That implies Hermes can kick off work without blocking the foreground interaction, which matters for engineers running long tasks, retries, or side jobs while continuing in the same session.

Nous has not paired that post with a formal changelog here, but the project messaging suggests the team is trying to make Hermes usable beyond a narrow power-user audience. The notable implementation detail in this evidence set is not a new model or benchmark; it is reduced operator friction inside the agent interface itself.

How hard is it to switch from OpenClaw?

The second concrete change is migration. According to the setup note, Hermes includes a migration script for OpenClaw users and can pull that path into initial setup, which is a much more practical onboarding story than asking teams to recreate local state and configuration by hand.

A supporting practitioner reaction in the migration praise repost frames the switch as “migrate easily,” but the stronger signal is the existence of the setup-time migration path itself. For engineers already testing agent shells side by side, that reduces the cost of trialing Hermes without tearing down an existing OpenClaw workflow.

Are people actually using it for real workflows?

The best adoption signal in this set is the OpenRouter chart repost, which shows Hermes Agent usage rising sharply over roughly the last month. The image labels Hermes Agent usage in the billions and ends near 14B, suggesting fast experimentation or sustained traffic rather than a one-day spike.

User anecdotes also point to broader-than-expected task execution. In one reposted account, a user says Hermes “started the project, recorded the clip, and sent it to my Telegram.” Another report in the Telegram voice-note example shows reminders being scheduled and a voice response being returned in chat. These are still anecdotal, but they show Hermes being used as a cross-tool agent rather than only a terminal wrapper.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 2 threads
How hard is it to switch from OpenClaw?1 post
Are people actually using it for real workflows?1 post
Share on X