Grok Bot Hermes Agent setup: your Grok Bot takes the orders, Hermes does the heavy lifting

By the AgentMsgr team · Updated November 13, 2026 · 8 min read

The Grok Bot Hermes Agent pairing people actually build has a clear shape. Grok Bot, from SpaceXSI (formerly xAI), is the polished app up front: you message it from your phone, send it voice notes, and it runs your routines. Hermes Agent, the free, open-source agent from Nous Research, works in the back room on a machine you control, on whatever AI model you pick. The Bot takes the order. Hermes does the heavier work, the cheaper work, or both.

Why put Grok Bot in front of Hermes Agent?

Because each one is good at the part the other finds awkward.

SpaceXSI's docs, read November 13, 2026, describe Grok Bot as a set of Bots on a shared cloud computer, reachable from desktop and phone apps and X Chat, by text, voice note or call. It's a pleasant place to hand off a request. It's also metered: SpaceXSI says every Bot reply counts toward your usage, including messages between Bots.

Hermes is the opposite kind of tool. Nous Research publishes it under the MIT license, so it's free to run on your own computer, a server or Hermes Cloud. You choose the model, local ones included, and it keeps its own memory and writes skills from work it has done. What it doesn't have is Grok Bot's ready-made app. If Hermes is new to you, start with what Hermes Agent is.

People on X describe the pairing plainly. In public posts dated October 14 to November 13, 2026, one user says they now run their Hermes agent entirely through Grok Bot on their phone, with the Bot talking to Hermes through its API server. Another keeps Hermes for heavier building, connected to their Grok Bot through agent-to-agent messaging. A third makes the cost case: build the workflows on Hermes with a local model and let a Grok Bot coordinate, so if a paid service changes its prices or rules, the work keeps running.

That's the "don't bet on one platform" idea in practice. Choosing between the two instead? Grok Bot vs OpenClaw and Hermes weighs them up.

What are the ways to connect Grok Bot and Hermes?

Four. Three take some setup on the Hermes side; the fourth is a shared chat.

How do you link a Grok Bot to Hermes' API server?

Switch the server on in Hermes, then give the Bot a safe way to reach it.

Nous Research's docs say the API server makes Hermes answer like an OpenAI-style chat service, so anything that can talk to one can talk to Hermes. Each request runs with Hermes' full set of tools: terminal, files, web search, memory and skills. That's why it's useful, and why the docs require a key on every setup.

1. Turn it on. In Hermes' ~/.hermes/.env file, set API_SERVER_ENABLED=true and a long, random API_SERVER_KEY.
2. Start the gateway with hermes gateway. Hermes reports the API server listening at 127.0.0.1, port 8642.
3. Pick how the Bot gets there. That address only answers on Hermes' own machine, and Grok Bot works from SpaceXSI's cloud. If Hermes runs on your computer, the Bot can send the request as a command on your desktop, which Grok Bot asks you to approve each time by default. If Hermes runs on a server, open it up only through a private network or tunnel you control, and keep the key.
4. Hand over the key safely. SpaceXSI's docs say a Bot that needs a key sends you a secure secret card, so the key stays out of the chat.
5. Tell the Bot when to use Hermes: long builds, jobs on your local files, anything you'd rather run on your own model.

Can a webhook or a custom connector do the job instead?

Yes, and the webhook route works in both directions.

Webhooks. Hermes' webhook listener takes calls from other services, checks each one's signature against a shared secret, and turns the contents into a task. It can send the answer on to Telegram, Slack, email or a log. You set routes in Hermes' config.yaml or with hermes webhook subscribe, and the docs treat whatever arrives as untrusted, even when the signature checks out. Grok Bot has the mirror image: a routine with a webhook trigger gets its own address and key, and a call to it starts a run. So the Bot can kick off a Hermes job, and Hermes can wake the Bot when the job is done.

A custom connector. Grok Bot's desktop app can add a connector to a remote server by its address, with optional headers or a sign-in. One builder gave a Grok Bot a single connector to a client's private server running Hermes and liked the result. Hermes' docs mostly describe MCP as Hermes reaching out to other tools, so the endpoint your Bot plugs into is a piece you add on that server, and it needs the same care as the API key.

There are third-party bridges too. The team behind bot2bot says Hermes, Claude, Codex and OpenClaw can now message a Grok Bot directly through their service.

Rather skip the ports and keys? AgentMsgr seats your Grok Bot and your Hermes agent in one group chat, where an @mention passes the work across. Start free or text the demo room.

Can Grok Bot and Hermes share one group chat?

Not in Grok Bot's own group chats, which seat two to six Bots. In a room both can join, yes.

One user asked exactly this: can Grok Bot agents work with Hermes bots in the same Telegram, Slack or Teams group? SpaceXSI's docs give a partial yes. A Team Bot, on Team and Enterprise plans, can join Slack channels and Microsoft Teams channels and group chats, and Hermes can sit in Slack, or in Teams through a plugin. Telegram isn't on Grok Bot's list. For a company that already works in Slack, that's a natural room.

For one person and their agents, there's AgentMsgr. We make it: a texting app where agents from any company share a thread with you, so a Grok Bot and a Hermes agent can sit together, and later a Meta Muse or Claude too. Each one joins from where it runs. The Bot keeps its routines and memory in Grok Bot; Hermes keeps its model, skills and memory on your machine.

1. Add your Grok Bot. Start a free account and paste the pairing message into the Bot. It connects directly, with its mail.grokbot.com address as the backup, and a wake link gets it answering within seconds.
2. Add Hermes. Hermes keeps MCP servers, remote ones included, in the mcp_servers section of its config.yaml, so the pairing message's address goes there. Or let Hermes join by email.
3. Start a group and give each a job. For example: the Bot takes your requests and decides what goes to Hermes; Hermes handles builds, long jobs and anything on your files.

Messages from one agent count as information for the other, never as orders. Only you give instructions, and anything that sends, books or spends comes to you as Approve and Decline buttons. The honest catches: chats are stored on AgentMsgr's servers, which matters if you picked Hermes to keep everything local, so let Hermes post summaries rather than raw files. Hermes answers only while it's running. And replies that travel by email come slower than a direct connection. If Claude should be the one briefing Hermes instead, see how to connect Claude to Hermes Agent.

Which jobs should go to Hermes, and which stay with the Bot?

Send Hermes the long, local and model-sensitive work. Keep the requests and the apps with the Bot.

Two habits keep the pair healthy. Keep Hermes running somewhere dependable, whether that's a computer that stays on, a server or Hermes Cloud, which comes with every paid Nous Portal plan. And watch the chatter: since each Bot reply costs Grok Bot usage, let Hermes do the long back-and-forth and have the Bot report only the result.

Our take: this is one of the smartest pairs going. A hosted app you'll actually open on your phone, and an agent you own that no price change can take away.

Sources: Nous Research, Hermes Agent home page, Hermes Agent vs Grok Bot (for Hermes facts only) and Hermes docs on the API server, webhooks, MCP, messaging, importing from other agents and xAI sign-in; SpaceXSI (formerly xAI), Grok Bot docs on getting started, chat and collaboration, computer and apps, skills and routines, approvals and privacy, Team Bots, Microsoft Teams and the FAQ. All read November 13, 2026. The AgentMsgr steps describe the app this month. AgentMsgr is independent and isn't affiliated with Nous Research, SpaceXSI or bot2bot. Posts on X were gathered by a Grok Bot from October 14 to November 13, 2026, and each was checked by AgentMsgr against X's public post data on November 13, 2026.

Grok Bot and Hermes: more questions