Can Build Remote Agent show a CodeNomad session on the phone?

No. CodeNomad is an Electron/Tauri/PWA cockpit for OpenCode. The phone lists native terminal windows only. Run Grok Build CLI (grok) in iTerm, Windows Terminal, or gnome-terminal on the same PC. That TTY is what the phone spectates. A CodeNomad SideCar pointed at 127.0.0.1:8788 shows Bot API JSON, not a transcript.

What is the CodeNomad plus Grok Build use case?

Keep CodeNomad as the OpenCode cockpit on the desk. Pair checksummed gbr-agent. In a native terminal run grok (Grok Build CLI). The phone running Build Remote Agent spectates and injects into that Grok Build window. Independent products; not affiliated.

Use case: CodeNomad + Grok Build CLI

CodeNomad is an unaffiliated OpenCode cockpit (Electron / Tauri / browser). Keep it on the desk. The phone spectates Grok Build CLI (grok) in a native terminal on that same PC. Protocol gbr/1. Independent product by Linespotting AB — not affiliated with Neural Nomads, xAI, or SpaceX.

Spec: docs/USE-CASE-CODENOMAD.md · integrations index · what the phone sees

Shape of the desk

Phone  (Build Remote Agent)
  │  HTTPS mailbox
  ▼
gbr-agent pair + run
  │  inject → discovered TTY
  ▼
Native terminal:  grok     ← roster item on the phone
CodeNomad app              ← OpenCode cockpit, not on the phone

The phone lists iTerm / Windows Terminal / gnome-terminal / conhost. It does not list CodeNomad tabs, OpenCode serve, 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 CodeNomad’s 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.
Open a real terminal window on that PC — not a CodeNomad SideCar.

Run Grok Build CLI in that window:

grok
# optional, so the phone title is obvious:
# /rename Phone Grok

Phone: that Grok Build window is on the roster. Inject types into it.
Leave CodeNomad running for OpenCode on the desktop. Same machine, different job.

Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1.

What fails (and why)

If you…	Phone sees
Add a CodeNomad SideCar to `http://127.0.0.1:8788`	Bot API JSON. Not a Grok Build transcript.
Expect CodeNomad Electron / PWA chat on the phone	Nothing — not a TTY. `gbr-agent` does not scrape Electron.
Run OpenCode TUI in a native terminal instead of `grok`	That OpenCode TTY (same attach). Headless `opencode serve` still hidden.
Use CodeNomad’s ttyd “Terminal” SideCar only	HTTP tab inside the cockpit — not an OS terminal window.

SideCars are for local web tools (OpenVSCode, ttyd) inside CodeNomad. They are not a pairing adapter. Pointing one at the Bot API does not put Grok Build on the phone.

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. CodeNomad’s job is the OpenCode cockpit — keep it. This page is a use case, not a CodeNomad adapter and not an endorsement.