Add Build Remote Agent phone pairing (gbr/1) - #12
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.
Reviewed by Cursor Bugbot for commit b361d8d. Configure here.
| }, | ||
| "gbr": { | ||
| "command": "node", | ||
| "args": ["GrokBuildRemote-Agents/mcp/gbr-mcp/bin/gbr-mcp.js"] |
There was a problem hiding this comment.
Broken GBR MCP script path
High Severity · Logic Bug
The new gbr MCP entry runs node with a relative path to gbr-mcp.js that is not shipped under the plugin (and is absent from this repo). Plugin MCP cwd defaults to the plugin root, so the process looks for that script beside mcp.json and fails to start, blocking the phone-pairing attach path this PR adds.
Reviewed by Cursor Bugbot for commit b361d8d. Configure here.
|
Still current — Build Remote Agent phone pairing via gbr/1 ( |


Add a Build Remote Agent pairing adapter so a phone can spectate this desktop session.
Protocol
gbr/1(unchanged). Phone is spectator + veto, not orchestrator.Install + pair
Phone: open Build Remote Agent → scan the QR or type the printed 8-char code.
Attach (only these)
http://127.0.0.1:8788aftergbr-agent runnode …/gbr-mcp/bin/gbr-mcp.js(clone GrokBuildRemote-Agents,npm installinmcp/gbr-mcp)Independent product by Linespotting AB. Not affiliated with xAI or SpaceX.
Do not commit mailbox keys. Phone Settings → Bot API is the only place a relay key is copied.
Note
Low Risk
Small MCP config-only change; no auth, data handling, or runtime logic is modified.
Overview
Adds a
gbrMCP server entry inplugins/starter-advanced/mcp.jsonso the starter-advanced plugin can talk to GrokBuildRemote via stdio (node …/gbr-mcp/bin/gbr-mcp.js). Existing postgres MCP config is unchanged.Reviewed by Cursor Bugbot for commit b361d8d. Bugbot is set up for automated code reviews on this repo. Configure here.