Research · Two packaging modes
What they are
Last updated: 2026-08-12
Two objects that share a word
❓ When someone says “Grok Bot” or “Hermes Agent Bot,” which stack object are they pointing at — a model, a harness, a host, or a looking glass?
A bot, in consumer language, is a named thing you message that then does work. That sentence hides four different machines:
- Cognition — a large language model proposing the next step.
- The constitutive agent — model + standing instructions + tools (what this house calls
*_agent_*). - The harness — the loop that keeps calling the model, dispatching tools, compressing context, and stopping.
- The host — the computer where those tools actually run.
Grok Bot and Hermes Agent Bots both sell the first sentence. They assemble the four machines differently.
Definition: A vendor-provided agent is a commercial SKU that ships a pre-assembled agent under the vendor’s control plane: model access, tools, managed loop, identity, often UI. It is a packaging mode, not a sixth stack layer.
Definition: An open process harness is software you run whose job is the loop. You bring (or rent) a model and a host.
Grok Bot is packaging mode (1). Hermes Agent is packaging mode (2). Hermes Bot Mode is a looking glass over (2). Confusing them is the first category error.
Grok Bot
❓ Is Grok Bot a chatbot, a coding agent, a custom-bot marketplace, or a teammate product on a cloud PC?
Official docs (retrieved 2026-08-25) define it without romance: “Bots are AI teammates you can give real work to.” A Bot is “a single persistent, named agent or one AI teammate.”[2]
It is not:
- Grok on X (the social looking glass).
- Grok Build (SpaceXAI’s coding-agent TUI / ACP product).[14]
- A public bot directory you install into other people’s chats (the 2023–2025 “custom Grok on X” idea).
It is:
- A desktop + iOS app (no Linux desktop client; the computer itself runs Linux).[4][5]
- Signed in with a Cursor account (or SuperGrok plans that include it).[4][24]
- A roster of named Bots that share one persistent cloud VM with browser, filesystem, and terminal.[2][3]
- Connectors shown as Plugins, plus MCP, plus computer use for sites with “no clean API or MCP.”[1][2]
- Skills (reusable how-to) and routines (when to run), including teach-by-demonstration when the control is on.[18]
- Group chats and bot-to-bot messaging so you are “not the router.”[1][2]
Launch: 11 August 2026, early beta.[1] Access expansion 21 August 2026: SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, Cursor Teams Standard and Premium.[24] Enterprise: waitlist / rolling out.[5]
The company name on the pages is SpaceXAI LLC; the lab lineage is xAI / Grok. This research treats xAI as the Party and Grok Bot as the PTC.
Hermes Agent, and what “Bot” means there
❓ Is a Hermes Bot a new runtime, or a costume on a profile?
Hermes Agent is Nous Research’s MIT-licensed harness: install on Linux/macOS/Windows, talk from CLI, Desktop, or a gateway into Telegram, Discord, Slack, WhatsApp, and 20+ other glasses.[8] It is provider-agnostic. It learns by writing skills. It remembers across sessions. It can spawn subagents, run cron, and run a durable Kanban board of profile workers.
Three different Hermes things get nicknamed “bot”:
| Nickname | What it actually is | Stack layer |
|---|---|---|
| Gateway bot | Hermes connected to Telegram/Discord/… as a messaging adapter | Looking glass |
| Kanban worker | A named profile process claiming durable tasks | Multi-agent orchestration |
| Bot Mode Bot | A Hermes profile rendered as a teammate in Desktop | Looking glass over harness + skills + memory |
Official Bot Mode docs are blunt: “A Bot is a Hermes profile — isolated config, memory, skills, credentials, and chat history under ~/.hermes/profiles/<name>/. Bot Mode is a UI over that primitive.”[21]
That is the opposite of Grok’s computer model. Hermes isolation is per Bot (profile). Grok isolation is per human account (one VM); Bots on that account are not security boundaries.[3][19]
Teknium shipped Bot Mode as a one-day public desktop plugin on 13 August 2026, then folded it into the monorepo (PR #87886) as default-on in v0.20.3 (~16 August).[22][23] GitHub release notes through v0.20.5 (v2026.8.19) keep tightening Bot Mode group rooms, avatars, and routing.[12]
Packaging-mode test
❓ If you cancelled the subscription tomorrow, what still runs?
| If you cancel… | Grok Bot | Hermes Agent |
|---|---|---|
| Subscription / Portal | The product stops. Computer, logins, routines are vendor-hosted. | Harness keeps running on your host with BYOK or local models. Portal-only Tool Gateway and Hermes Cloud stop. |
| Desktop app | You lose the looking glass; cloud work is designed to continue while the laptop is closed.[3] | CLI/gateway can outlive Desktop. Bot Mode is Desktop-only UI. |
| Model vendor | There is no model picker; SpaceXAI routes a fixed set.[5] | Swap /model mid-session. |
Hard-to-vary test: You cannot explain Grok Bot as “Grok with plugins” without the always-on VM — that is the product. You cannot explain Hermes Bot Mode as “a new agent runtime” without the profile — the UI owns no data.[21]
Refutability: This pairing fails if Grok ships per-bot VMs with separate credentials, or if Hermes Bot Mode becomes a closed hosted SKU that you cannot run without Portal.
Reach example: Copilot Cowork and Claude-class desktop agents sit in the same packaging fork: suite-managed computer vs. open harness on your host.
Criticism note: “Bot” in both brands is a marketing compression. Architects should say harness, host, and glass out loud or they will buy the wrong layer.