Does Open Interpreter or Local CLI appear on the phone after pairing?

Yes, if you run interpreter / i or local-cli in a native terminal window (iTerm, Windows Terminal, gnome-terminal, conhost) after gbr-agent pair and run. The phone lists that TTY. Headless HTTP UIs do not: Open Interpreter --remote or ACP-in-editor, Local CLI Electron desktop, Ollama WebUI, LM Studio GUI, Open WebUI, or a browser tab on :8788.

Is Build Remote Agent affiliated with Open Interpreter or Local CLI?

No. Independent product by Linespotting AB. Open Interpreter (openinterpreter/openinterpreter) and Local CLI (HanSyngha/Local-CLI) are unaffiliated. This page is a use case, not an adapter and not an endorsement. Other repos should link to grokbuildremote.com/integrations, not copy install.sh.

Use case: Open Interpreter / Local CLI

Open Interpreter and Local CLI are unaffiliated local-LLM coding agents. Run them in a native terminal on the PC. After gbr-agent pair + run, that TTY appears on the phone. Headless HTTP UIs do not. Protocol gbr/1. Independent product by Linespotting AB — not affiliated with Open Interpreter, Local CLI, xAI, or SpaceX.

Integrations index · pinned install · what the phone sees

Shape of the desk

Phone  (Build Remote Agent)
  │  HTTPS mailbox
  ▼
gbr-agent pair + run
  │  inject → discovered TTY
  ▼
Native terminal:  interpreter   ← roster item on the phone
              or  local-cli     ← same attach
Electron / --remote / WebUI     ← not on the phone

The phone lists iTerm / Windows Terminal / gnome-terminal / conhost. It does not list Local CLI’s Electron chat, Open Interpreter --remote / ACP-in-editor, Ollama WebUI, LM Studio, or Open WebUI.

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 Open Interpreter or Local CLI 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 the Electron app, not a browser tab.

Run the CLI in that window:

# Open Interpreter (current: i or interpreter)
interpreter
# or: i

# Local CLI (npm: local-cli-agent)
local-cli

Phone: that window is on the roster. Inject types into it.
Leave any HTTP UI (Electron, LM Studio, Ollama WebUI) on the desk. Same machine, different job.

Same attach for other local-LLM CLIs in a native TTY: omp (oh-my-pi), pi, vtcode, meer, ollama run. Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1.

What fails (and why)

If you…	Phone sees
Run Open Interpreter `--remote` / ACP-in-editor / HTTP app-server	Nothing useful — not an OS terminal window.
Use Local CLI’s Electron desktop (Chat Window / Task Popup)	Nothing — not a TTY. `gbr-agent` does not scrape Electron.
Point a browser at `http://127.0.0.1:8788`	Bot API JSON. Not an interpreter transcript.
Drive Ollama WebUI, Open WebUI, or LM Studio GUI	Headless HTTP UI. Run the model from a CLI in a terminal if you want it on the phone.

Headless HTTP UIs stay on the desk. Pairing the mailbox does not tunnel a web UI to the phone. Run interpreter or local-cli in iTerm / Windows Terminal / gnome-terminal.

Why a native TTY

Build Remote Agent’s native attach is inject into a terminal. Open Interpreter (interpreter / i) and Local CLI (local-cli) are TUIs with a window title, so they show up on the roster. Their Electron / --remote / WebUI surfaces are a different job — keep them. This page is a use case, not an adapter and not an endorsement. Other GitHub repos: a short unaffiliated link to grokbuildremote.com/integrations is enough. Do not copy install.sh.