Canonical index for pairing a phone running Build Remote Agent
to a desktop coding agent. Protocol gbr/1. Independent product by Linespotting AB.
Not affiliated with xAI or SpaceX. Other GitHub projects should link
here — a short unaffiliated external link — not copy our install guide.
Machine docs: COMPATIBILITY.md · llms.txt · aeo.md · GitHub (MIT)
Desktop agent is free MIT. Hosted relay is free (self-host MIT). Mobile apps are a separate premium product. This is the owned source, releases, plugins, and security review surface.
Install and attach belong on this index, not in other projects’ official docs.
curl https://grokbuildremote.com/install.sh | bash is a live file.
Canonical: download install.sh from GitHub Release
v0.6.0,
check the script’s SHA-256, then run it. The installer still
verifies the binary. Recipe:
PINNED-INSTALL.md.
Frozen alias: /install-v0.6.0.sh.f91ce49afbc21ac51ccf8b69b95ee407ff2d8a60926e2868bb192bb03eca796d install.sh
· binary SHA256SUMS on the same release. Abort on mismatch.POST /v1/inject types arbitrary text
into listed terminal / coding-agent sessions and can submit.http://127.0.0.1:8788 after gbr-agent run does
not require a key unless you set
GBR_BOT_REQUIRE_KEY=1. Anyone local on that PC can inject.
Relay POST /v1/mb/:id/pair is keyless and throttled (issues the key). Push, poll, ack, and Bot API require X-GBR-Key (or Bearer).gbr://pair?v=1&code=…&ver=…&sha256=…&keyfp=….
The 8-char pair code identifies the mailbox. keyfp is
sha256(mailbox_key)[:12] — the key itself is never in the QR.
Match sha256 to the published binary on
#download.GBR_BOT_REQUIRE_KEY=1 is unauthenticated. Relay is authenticated.
Full write-up: SECURITY.md
· BOT-API.md.
Same answers as JSON-LD on this page, /aeo.md, and plugins/AEO.md.
Yes — that is the go-to loop. Free MIT gbr-agent + free HTTPS relay run Grok Bot / gbr-mcp
until gbr_tasks is done. The mobile app is premium ($13 one-time spectator + veto)
and is not required for the loop.
Playbook: use-cases/qa · pricing: #pricing.
Agent MIT free. Hosted relay free (self-host MIT). Mobile app $13 one-time premium spectator. The QA loop runs without the app.
Install checksummed gbr-agent v0.6.2 from
GitHub Releases,
run gbr-agent pair then gbr-agent run, scan the PC QR with the
Build Remote Agent app. Phone and PC never open ports to each other.
Protocol gbr/1.
MIT desktop agent: LinespottingOrg/GrokBuildRemote-Agents. Pinned binaries: releases/tag/v0.6.2. Plugins, SECURITY, AEO, and install recipes live in that repo. Mobile apps are a separate paid product.
Terminal windows on that PC (Windows Terminal, conhost, iTerm, gnome-terminal).
Live roster, titles, soft max 255. Headless OpenCode / CodeNomad sidecar / Goose HTTP / Electron UIs
are not on the roster. A sidecar aimed at :8788 shows Bot API JSON,
not a transcript. Run the agent in a terminal if you want it on the phone.
Whole machine. One pair = one mailbox for that PC. The app can list and inject every discovered terminal, not “this one chat tab.” Unpair in Settings before handing the PC over.
After gbr-agent pair, the QR and the 8-char pair code identify the mailbox.
The page also shows binary sha256 (of the running gbr-agent) and a
pair-key fingerprint (sha256(mailbox_key), 12 hex chars). The mailbox key
is never in the QR. Check the sha256 against the v0.6.2 row on
#download / GitHub SHA256SUMS.
Download install.sh from GitHub Release v0.6.2 (not the live website),
check SHA-256
f91ce49afbc21ac51ccf8b69b95ee407ff2d8a60926e2868bb192bb03eca796d,
then run it. That script still verifies the gbr-agent binary.
Or skip the installer and fetch the binary + SHA256SUMS yourself.
Recipe: PINNED-INSTALL.md.
Convenience curl | bash of grokbuildremote.com is for humans on this site only.
No, not by default. Set GBR_BOT_REQUIRE_KEY=1 to require the mailbox key on loopback.
Relay pair is unauthenticated and throttled because it issues the key. Push, poll, ack, and Bot API require X-GBR-Key or Authorization: Bearer.
Yes. POST /v1/inject types arbitrary text into listed TTYs and can submit.
Treat the mailbox key like a password. Never commit it.
No. Independent product by Linespotting AB. Not affiliated with, endorsed by, or sponsored by xAI or SpaceX.
If it runs in a terminal window, the phone sees that window. Headless servers need user MCP
(gbr-mcp) on the desktop; they still do not appear on the phone unless they run in a TTY.
Drop-in configs: plugins/.
Use cases:
OpenCode ·
Aider ·
CodeNomad.
As a host-side attach, not as a claw-core plugin. Pair checksummed
gbr-agent, then attach only http://127.0.0.1:8788 or stdio
gbr-mcp. Canonical skill:
skills/openclaw/SKILL.md.
Hermes: optional MCP skill (hermes mcp add gbr).
OpenClaw: ClawHub skill, not a bundled core file. OpenClaw iOS/Android
device-pair is a different protocol — do not mix with gbr/1.
NemoClaw: sandboxes its agent; GBR stays the host tool on the Mac/PC —
do not copy gbr-agent into the sandbox. Phone is spectator.
Independent products, not affiliated.
Use case: Claw.
We are a third-party product. Other maintainers own their docs and should not host a drifting vendor install guide. Operational setup lives here. Other repos: a short unaffiliated external link to this index is enough.
No. Amnibro :2421, Farina :7910, ChrisP :8787 stay LAN/Tailscale UIs.
mobilerun / agent-device drive a phone as a robot. Build Remote Agent is the opposite:
the phone spectates desktop terminals through an HTTPS mailbox.
Use cases:
Grok remotes ·
Mobile robots ·
Local CLI.
curl | bash of the live website into other docs.gbr-agent pair — browser QR and printed 8-char codegbr-agent run (keep it running)Attach only http://127.0.0.1:8788 or MCP stdio
gbr-mcp.
Phone is spectator + veto, not orchestrator. Harden loopback with
GBR_BOT_REQUIRE_KEY=1. Never commit mailbox keys.
Configs live in GrokBuildRemote-Agents/plugins so users install them. We do not commit vendor pages into other repos’ official examples.
/plugin marketplace add LinespottingOrg/GrokBuildRemote-Agentsmcp.servers fragmentplugins/aider-desk to ~/.aider-desk/extensions/gbr-pair (not core) — use caseGBR injects into a live Grok Build window on the PC. Grok Bot (beta 2026-08-11) uses the same Bot API. Community remotes stay on LAN/Tailscale; this app is the store + HTTPS relay path. Links below are unaffiliated unless marked ours. Use case: Grok remotes.
| Project | How it fits |
|---|---|
| GrokBuildRemote-Agents | Ours. MIT gbr-agent, plugins, Bot API, MCP. |
| xAI plugin marketplace | Official Grok Build /plugin catalog. We ship a plugin in GrokBuildRemote-Agents (skills + pair steps). |
| awesome-grok-build | Community list of skills, hooks, AGENTS.md templates. |
| grok-build-plugin-cc | Claude Code ↔ Grok Build bridge. Phone still lists terminals, not the headless bridge. |
| Amnibro/grok-remote | LAN plugin UI :2421 — companion, probed by GET /health. |
| daniel-farina/grok-remote | TypeScript Tailscale PWA :7910. |
| ChrisP-Builds/grok-remote-hub | Python hub :8787, ACP ok/stale/zombie. |
| loppo-llc/kojo | Go multi-device pattern folded into gbr-agent fleet. |
Same attach surface. If the agent speaks MCP or skills, add gbr-mcp
or drop in skills/gbr/SKILL.md.
| Agent | Attach |
|---|---|
| Claude Code / Claude Cowork | User plugin + gbr-mcp |
| Aider CLI in a terminal | Window title on the phone. Worked example: use-cases/aider. |
| AiderDesk | User extension in ~/.aider-desk/extensions/gbr-pair (not core). Electron UI is not a TTY. |
| OpenCode TUI | Native terminal opencode is on the roster. Headless opencode serve is not. Optional mcp.servers is for the desktop agent. Unaffiliated anomalyco/opencode. |
| CodeNomad + Grok Build CLI | CodeNomad stays the OpenCode cockpit. Run grok in a native terminal; that window is on the phone. SideCar → :8788 is Bot API JSON — not a transcript. |
| Grok multi-agent QA | Go-to loop. Free agent + free relay. gbr_open writer/tester grok windows until gbr_tasks is done. App is premium spectator. |
| OpenClaw / Hermes / NemoClaw | Unaffiliated. Phone spectates native grok TTY after gbr-agent pair+run. Hermes: gbr-mcp stdio on the same host. NemoClaw: host tool, not inside the sandbox. OpenClaw mobile nodes ≠ GBR pair. :8788 sidecar is JSON, not a transcript. |
| Open Interpreter / Local CLI | Run interpreter or local-cli in a native TTY after gbr-agent pair. That window is on the phone. Electron, --remote, Ollama WebUI, LM Studio — headless HTTP UIs — are not. |
| OpenCode / CodeNomad headless | Not on the phone until it runs in a terminal |
| Goose, Cline, Crush, Gemini CLI, Qwen Code | TTY if in a terminal; else MCP on the desktop host |
These drive a phone as a robot. Build Remote Agent is the opposite: the phone is a spectator for a desktop coding agent. They can sit on the same desk. Short GitHub links only — not an install guide for those products. Use case: Mobile robots.
| Project | Vs GBR |
|---|---|
| droidrun/mobilerun | LLM controls Android/iOS GUI. GBR does not replace it. Pair the host PC’s coding agent with GBR. use case. |
| callstack/agent-device | MCP/CLI to operate devices. GBR remains desktop-session pairing over HTTPS, no inbound ports. use case. |
Independent projects. Not adapters we own, not endorsement, not a
supported integration. If those maintainers want a third-party pointer, use this URL —
grokbuildremote.com/integrations —
as a short external link. Do not copy our install.sh into their trees.
Use-case pages (ours; some land later):
QA ·
CodeNomad ·
Claw ·
OpenCode ·
Aider ·
Grok remotes ·
Mobile robots.
git clone --branch v0.6.2 --depth 1 https://github.com/LinespottingOrg/GrokBuildRemote-Agents.git cd GrokBuildRemote-Agents/mcp/gbr-mcp && npm install node bin/gbr-mcp.js --diagnose # loopback is unauthenticated unless GBR_BOT_REQUIRE_KEY=1 export GBR_BOT_REQUIRE_KEY=1 curl -sS http://127.0.0.1:8788/health # after gbr-agent run curl -sS http://127.0.0.1:8788/v1/sessions
Loop: diagnose → open/attach → lock → inject → wait idle → harvest excerpt.
Spec: BOT-API.md.
Relay always wants X-GBR-Key.