Download on the App Store Get it on Google Play

Use case: mobile robots vs desktop spectator

droidrun/mobilerun and callstack/agent-device drive a phone as a robot — an LLM or MCP taps Android / iOS GUI. Build Remote Agent is the opposite: the phone spectates a desktop TTY (protocol gbr/1). Independent product by Linespotting AB — not affiliated with DroidRun, Callstack, xAI, or SpaceX.

Canonical index: integrations · short unaffiliated GitHub links only — do not copy install.sh into their docs. what the phone sees

Opposite directions

PC  (LLM / MCP / CLI)
  │  ADB · XCTest · device MCP
  ▼
Phone GUI                 ←  mobilerun / agent-device DRIVE this

Phone  (Build Remote Agent)
  │  HTTPS mailbox  gbr/1
  ▼
gbr-agent pair + run
  │  inject → discovered TTY
  ▼
Native terminal: grok / claude / aider   ←  phone SPECTATES this

They can sit on the same desk. They are not substitutes. GBR never taps the Android / iOS GUI. mobilerun / agent-device never list desktop terminals on a Build Remote Agent roster.

Unaffiliated projects

ProjectJob
droidrun/mobilerun LLM controls Android / iOS GUI. The phone is the robot.
callstack/agent-device MCP / CLI to operate devices. The phone is the robot.
Build Remote Agent Phone spectates desktop terminals through an HTTPS mailbox. No inbound ports.

Other maintainers: one short external link to grokbuildremote.com/integrations is enough. Do not host our installer, checksums, or curl | bash.

Walkthrough (the GBR direction)

  1. 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 mobilerun or agent-device docs.
  2. PC: gbr-agent pair then gbr-agent run. Scan the QR with Build Remote Agent.
  3. Open a real terminal window on that PC. Run the coding agent there (grok, Claude Code, Aider, OpenCode TUI, …).
  4. Phone: that window is on the roster. Inject types into it.
  5. If you also need a phone-as-robot, keep mobilerun / agent-device for that job. Same machine is fine. Different attach surface.

Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1.

What fails (and why)

If you…What happens
Expect GBR to tap Android / iOS like mobilerun Nothing — GBR lists desktop TTYs only.
Expect mobilerun / agent-device to show Grok Build on a spectator phone Wrong direction. They drive a device GUI; they are not a gbr/1 mailbox.
Copy install.sh into those repos’ docs A mutable vendor installer in someone else’s tree. Link /integrations instead.
Point a phone-robot MCP at 127.0.0.1:8788 Bot API JSON, not a GUI stream and not a desktop transcript on the phone.
This page is a use-case contrast, not an adapter and not an endorsement. Pairing, checksums, and trust live on grokbuildremote.com/integrations.