Are OpenClaw, Hermes, and NemoClaw affiliated with Build Remote Agent?

No. OpenClaw, Hermes (Nous Research), and NVIDIA NemoClaw are independent products. Build Remote Agent is an independent product by Linespotting AB. This page is a use case, not an official adapter and not an endorsement.

Can the phone show an OpenClaw, Hermes, or NemoClaw session?

The phone lists native terminal windows only. After gbr-agent pair and gbr-agent run, run Grok Build CLI (grok) in iTerm, Windows Terminal, or gnome-terminal. That TTY is what the phone spectates. A sidecar pointed at 127.0.0.1:8788 shows Bot API JSON, not a transcript. OpenClaw mobile nodes are not a GBR pair.

How does Hermes attach?

On the same host as gbr-agent run, attach gbr-mcp over stdio (hermes mcp add gbr -- stdio -- node …/gbr-mcp.js). Then gbr_open spawns Grok Build CLI. Do not register http://127.0.0.1:8788 as MCP — that is Bot API REST. Set GBR_BOT_REQUIRE_KEY=1 for loopback inject.

Can I run gbr-agent inside a NemoClaw sandbox?

No. NemoClaw sandboxes its agent. GBR is the host tool on the Mac/PC. Point NemoClaw at loopback :8788 or gbr-mcp on the host. Do not copy gbr-agent into the sandbox and do not invent a second pair protocol.

Use case: OpenClaw / Hermes / NemoClaw

OpenClaw, Hermes, and NemoClaw are unaffiliated. Keep them as their own agents. The phone spectates Grok Build CLI (grok) in a native terminal on the host after gbr-agent pair + gbr-agent run. Protocol gbr/1. Independent product by Linespotting AB — not affiliated with OpenClaw, Nous Research, NVIDIA, xAI, or SpaceX.

Skills: openclaw · hermes · nemoclaw · setup: scripts/setup-gbr-mcp.sh · integrations

Shape of the desk

Hermes / OpenClaw / NemoClaw (MCP client)
  │  stdio gbr-mcp   ← NOT http://127.0.0.1:8788 (that is Bot API REST)
  ▼
gbr-agent run
  │  gbr_open → spawns `grok` in a TTY
  ▼
Grok Build CLI window         ← phone roster after pair
NemoClaw sandbox              ← its agent stays inside; GBR stays on the host

The phone lists iTerm / Windows Terminal / gnome-terminal / conhost. It does not list OpenClaw mobile nodes, NemoClaw sandboxes, or a sidecar on port 8788.

Walkthrough

Install checksummed gbr-agent v0.6.0 — PINNED-INSTALL.md (verify the installer SHA-256, then the binary). Do not paste live curl | bash into OpenClaw / Hermes / NemoClaw docs.
PC: gbr-agent pair then gbr-agent run. Scan the QR with Build Remote Agent. Optional: match binary sha256 / pair-key fingerprint on the pair page to #download.
Pin MCP: bash scripts/setup-gbr-mcp.sh (clones tag v0.6.0, not default branch). Then add stdio gbr-mcp to Hermes / OpenClaw / NemoClaw-on-host.

From the claw agent, drive Grok Build CLI:

gbr_diagnose
gbr_open          # command defaults to grok — this is what makes grok work
gbr_inject        # submit=true, holder=hermes|openclaw|nemoclaw
gbr_result        # wait_ms=60000

That gbr_open spawns a native grok TTY. The phone lists it. You can also run grok yourself in iTerm / Windows Terminal.

Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1.

Hermes — gbr-mcp stdio on the same host

Hermes does not need to be installed inside the GBR tree. On a Hermes box that already has gbr-agent run:

bash scripts/setup-gbr-mcp.sh
hermes mcp add gbr -- stdio -- node $HOME/.gbr/gbr-mcp-src/mcp/gbr-mcp/bin/gbr-mcp.js
# then: gbr_open → grok CLI. Do NOT add http://127.0.0.1:8788 as MCP (Bot API REST).

Attach is stdio on the host that runs gbr-agent. gbr_open is what starts Grok Build CLI for Hermes to inject into.

NemoClaw — host tool, not inside the sandbox

NemoClaw sandboxes its agent (OpenClaw / Hermes / others). GBR is the host tool on the Mac/PC. Run gbr-mcp stdio on the host (or Bot API :8788 with GBR_BOT_REQUIRE_KEY=1). Then gbr_open spawns grok on the host TTY. Do not copy gbr-agent into the sandbox. Do not invent a second pair protocol.

Sandbox guest ≠ paired PC. The phone mailbox is the machine running gbr-agent pair + run, not a container inside OpenShell.

OpenClaw mobile nodes ≠ GBR pair

OpenClaw can run nodes on phones and chat apps. That is OpenClaw’s own mesh. It is not gbr-agent pair. Build Remote Agent pairing is: PC QR (or 8-char code) → this app → HTTPS mailbox → inject into a desktop TTY. Do not scan an OpenClaw node QR and expect a GBR roster.

What fails (and why)

If you…	Phone sees
Register `http://127.0.0.1:8788` as an MCP server	Wrong protocol. That URL is Bot API REST. MCP is stdio `gbr-mcp`. Then `gbr_open` starts `grok`.
Point a sidecar / SideCar at `http://127.0.0.1:8788`	Bot API JSON. Not a Grok Build transcript.
Treat an OpenClaw mobile node as a GBR pair	Nothing GBR-related — different protocol. Pair with `gbr-agent pair`.
Install `gbr-agent` inside a NemoClaw sandbox	Wrong place. GBR stays on the host; the sandbox is for NemoClaw’s agent.
Paste live `curl \| bash` of grokbuildremote.com into Claw docs	Mutable remote install. Pin GitHub Release v0.6.0 and verify SHA-256.
Expect OpenClaw / Hermes Electron or chat UI on the phone	Nothing — not a TTY. Run `grok` in a native terminal.

:8788 is the Bot API. A sidecar aimed at it is JSON, not a transcript. Pin PINNED-INSTALL.md — do not use live curl | bash as the trust root.

Why Grok Build CLI

Build Remote Agent’s native attach is inject into a terminal. Grok Build is a TUI you run as grok. That is a window with a title, so it shows up on the roster. OpenClaw / Hermes / NemoClaw keep their own jobs on the host (or in NemoClaw’s sandbox). This page is a use case, not a Claw adapter and not an endorsement.