How you ask and steer
- Conversation and personal context
- Messaging channels and notifications
- Interactive planning and follow-up
- Assistant-specific skills and memory
Grex + your AI assistant
Keep your assistant. Add accountable execution.
OpenClaw, Hermes Agent, Grok Bot, and other assistants give you different ways to work with AI. Grex belongs underneath them: running durable missions on hardware you control, bounding the work, checking the evidence, and recording the outcome.
Your assistantConversation, context, channels
GrexMissions, controls, evidence
Different jobs
The assistant is the command surface. Grex is the mission system.
How consequential work runs
- Durable mission state across days
- Owned execution fleet and worker coordination
- Spend, time, value, and attention limits
- Evidence, ratification, and signed receipts
Choose the experience you prefer
Three assistants. Three useful combinations.
Personal assistant
Control path demonstratedOpenClaw + Grex
Talk to your AI from anywhere. Let Grex run the consequential work.
- OpenClaw adds
- Messaging channels, personal context, memory, routines, and an always-available assistant.
- Grex adds
- A bounded mission, owned worker fleet, economics, verification, and a durable outcome record.
- Good fit
- Starting and checking a multi-day mission from the same assistant you use for daily life.
The MCP control path has been demonstrated. Turnkey onboarding and ongoing compatibility certification are still being productized.
Open autonomous agent
Pairing guide plannedHermes Agent + Grex
Let Hermes reason, learn, and automate. Let Grex define what counts as success.
- Hermes adds
- Skills, memory, browser and terminal tools, delegated agents, routines, and durable task boards.
- Grex adds
- Mission-level economics, independent evidence requirements, ratification, fleet controls, and receipts.
- Good fit
- Using a powerful open agent to drive research or operations that need independently checkable outcomes.
Hermes Agent supports MCP-based tools. A formal Grex pairing guide and compatibility certification are planned.
Cloud AI teammate
Pairing guide plannedGrok Bot + Grex
Use a polished cloud teammate to direct work running on infrastructure you control.
- Grok Bot adds
- A persistent cloud computer, browser and SaaS connections, routines, and cooperating named bots.
- Grex adds
- Owned mission compute, long-duration execution, hard operating limits, evidence, and outcome accountability.
- Good fit
- Directing owned compute from a convenient cloud assistant while keeping the mission record in Grex.
Grok Bot exposes integration paths including MCP. A formal Grex pairing and compatibility certification are planned.
Capability comparison
Compare the role each product plays.
This is not a winner-take-all table. It shows where each product is strongest and what Grex adds when the work becomes consequential.
| Product | Primary job | Best use | What Grex adds |
|---|---|---|---|
| OpenClaw | Self-hosted personal assistant | Messaging, daily workflows, personal automation, and access from many channels | Accountable missions that keep running beyond the conversation |
| Hermes Agent | Open, general-purpose autonomous agent | Skills, research, coding, browser work, automation, and multi-agent task boards | Business outcome contracts, fleet-wide controls, independent ratification, and receipts |
| Grok Bot | Persistent cloud AI teammate | Turnkey browser, SaaS, knowledge-work, and team workflows | Owned mission compute and an independently checkable outcome record |
| Grex | Accountable mission execution | Important work that runs for hours, days, or continuously | Use the assistant experience you prefer instead of replacing it |
How they work together
One conversation can start a mission that outlives the conversation.
- 01
You describe the outcome in the assistant you already use.
- 02
The assistant creates or steers a bounded mission through Grex.
- 03
Grex coordinates workers and persists the mission outside the chat context.
- 04
Your assistant reports status; Grex remains authoritative for evidence, gates, and completion.
Compatibility is a product commitment, not a blanket claim.
Grex is moving toward assistant-agnostic operation over MCP. Named pairings are published as supported only after their mission-control path and safety behavior are verified.
Frequently asked questions
Grex and AI assistants
Does Grex replace OpenClaw?
No. OpenClaw can remain your personal assistant and messaging surface. Grex adds bounded, durable, verified mission execution underneath.
Can Hermes Agent drive Grex missions?
That is the intended assistant-agnostic model. Hermes Agent supports MCP-based tools; the formal pairing guide and compatibility certification are still planned.
Does Grex replace Grok Bot?
No. Grok Bot can provide the cloud assistant experience while Grex provides owned mission compute, operating limits, evidence, and receipts.
Is Grex itself an AI assistant?
No. Grex is the accountable execution and mission-control layer for long-running AI work. The assistant is how the operator asks, steers, and checks in.
Can any MCP-capable assistant use Grex?
Assistant-agnostic MCP control is the product direction. Specific assistants still require verified onboarding and compatibility testing before Grex labels the pairing supported.
Product descriptions are based on the public documentation for OpenClaw, Hermes Agent, and Grok Bot.
Keep the assistant you prefer. Give consequential work a system of record.
Share your interest