Does Build Remote Agent replace Amnibro, Farina, or ChrisP grok remotes?

No. Amnibro :2421, Farina :7910, and ChrisP :8787 stay LAN/Tailscale companion UIs. Build Remote Agent is the store app plus GitHub HTTPS relay so a phone can spectate desktop terminals through firewalls. Independent products; not affiliated.

How does GET /health see companion remotes?

After gbr-agent run, GET http://127.0.0.1:8788/health (or GET /v1/health) probes loopback only: Amnibro :2421, Farina :7910/api/health, ChrisP hub :8787/health. Companions that are not listening report quality down. GBR Bot API stays on :8788 so it does not collide with ChrisP :8787. We do not replace the GitHub relay with Tailscale.

Use case: Amnibro, Farina, ChrisP stay companions

Unaffiliated. Amnibro/grok-remote, daniel-farina/grok-remote, and ChrisP-Builds/grok-remote-hub are independent community remotes. Build Remote Agent does not replace them, does not ship inside them, and is not affiliated with those projects, xAI, or SpaceX. Independent product by Linespotting AB. Protocol gbr/1.

Canonical index: integrations · homepage ecosystem · BOT-API.md (GET /health).

Two jobs on one desk

LAN / Tailscale UI          Store app + GitHub HTTPS relay
─────────────────────       ────────────────────────────────
Amnibro     :2421           Phone (Build Remote Agent)
Farina      :7910             │  HTTPS mailbox  (gbr/1)
ChrisP hub  :8787             ▼
                            gbr-agent pair + run
                              │  Bot API :8788
                              ▼
                            Native terminal: grok / CLI
                            GET /health probes companions
                            on loopback only

Amnibro, Farina, and ChrisP stay LAN/Tailscale companions. Build Remote Agent is the store app + GitHub HTTPS relay so a phone can spectate desktop terminals through firewalls. No fourth pair protocol. We do not replace the GitHub relay with Tailscale.

Ports (do not collide)

Who	Bind	Path GBR probes	Stays
Amnibro/grok-remote	`:2421`	`/`	LAN ACP plugin UI (`/remote`)
daniel-farina/grok-remote	`:7910`	`/api/health`	TypeScript Tailscale PWA
ChrisP-Builds grok-remote-hub	`:8787`	`/health`	Python hub, ACP `ok/stale/zombie`
Build Remote Agent (ours)	`:8788`	`GET /health` (watchdog)	Store app + GitHub HTTPS relay + Grok Bot

ChrisP hub is :8787. GBR Bot API is :8788. Both can run. Companion probes are loopback-only and short-timeout so /health never blocks Grok Bot.

`GET /health` probes

After gbr-agent run, the watchdog lists which companions are up on this PC:

curl -sS http://127.0.0.1:8788/health
# same document: GET /v1/health

JSON includes roster quality ok / stale / zombie (ChrisP vocabulary) and a companions array: amnibro:2421, farina:7910, chrisp:8787. Online = TCP listen + HTTP 2xx–4xx on that path. Down = not listening. The note on the snapshot is: GitHub HTTPS relay is the control plane; companion remotes are optional LAN/Tailscale hubs on this PC.

Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1. Relay pair is keyless and throttled; push, poll, ack, and Bot API require X-GBR-Key.

Walkthrough

Leave the companion you already use running — Amnibro on :2421, Farina on :7910, ChrisP on :8787. Same Wi-Fi or Tailscale for their UI.
Install checksummed gbr-agent v0.6.2 — PINNED-INSTALL.md. Do not paste live curl | bash into those remotes’ docs.
PC: gbr-agent pair then gbr-agent run. Scan the QR with Build Remote Agent.
Phone: spectates native terminal windows (Grok Build / CLI) through the GitHub HTTPS mailbox. That path works through firewalls; no inbound ports.
Optional: curl -sS http://127.0.0.1:8788/health — companions show up or down. Grok Bot and the website can see the whole desk.

What not to do

Tempting	Why it fails
Replace Amnibro / Farina / ChrisP with GBR	Different job. They are LAN/Tailscale UIs. GBR is store + HTTPS relay.
Point a companion at `:8788` as if it were a chat	Bot API JSON, not a Grok Build transcript.
Move GBR Bot API onto `:8787`	Collides with ChrisP hub. GBR stays `:8788`.
Invent a fourth pair protocol / reuse Tailscale as `gbr/1`	Pair is still `gbr-agent pair` + QR. Relay stays GitHub HTTPS.
Expect GBR to open inbound LAN ports	Phone and PC never open sockets to each other.

This page is a use case, not an adapter and not an endorsement. Other GitHub trees: a short unaffiliated link to /integrations.html — do not copy install.sh.