Does Build Remote Agent show Aider CLI on the phone?

Yes, when Aider CLI (aider) runs in a native terminal on the paired PC. The phone lists that window title and injects into it. Protocol gbr/1. Independent product — not affiliated with Aider-AI or hotovo.

Is the AiderDesk pairing an official AiderDesk core feature?

No. It is a user extension. Copy GrokBuildRemote-Agents plugins/aider-desk to ~/.aider-desk/extensions/gbr-pair. Do not land it in AiderDesk core. The Electron UI is not a TTY and will not appear on the phone roster.

Should I paste curl | bash into Aider or AiderDesk docs?

No. Pin GitHub Release v0.6.0, verify the installer SHA-256, then the binary. Live curl|bash of grokbuildremote.com/install.sh is mutable convenience only. See PINNED-INSTALL.md.

Use case: Aider CLI + AiderDesk

Aider CLI in a native terminal is on the phone. That window is a TTY, so gbr-agent lists it and injects into it. AiderDesk is a user extension at ~/.aider-desk/extensions/gbr-pair — not core. The Electron UI is not a TTY. Protocol gbr/1. Independent product by Linespotting AB — not affiliated with Aider-AI, hotovo, xAI, or SpaceX.

Index: integrations · pinned install (not curl | bash) · what the phone sees · plugins/aider-desk

Shape of the desk

Phone  (Build Remote Agent)
  │  HTTPS mailbox
  ▼
gbr-agent pair + run
  │  inject → discovered TTY
  ▼
Native terminal:  aider          ← roster item on the phone
AiderDesk Electron UI            ← not a TTY, not on the phone
  └── ~/.aider-desk/extensions/gbr-pair   ← user extension, not core

The phone lists iTerm / Windows Terminal / gnome-terminal / conhost running aider. It does not list AiderDesk tabs, the AiderDesk REST port, or a core AiderDesk plugin.

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 Aider or AiderDesk 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 an AiderDesk panel.

Run Aider CLI in that window:

aider
# the window title is what the phone lists

Phone: that Aider CLI window is on the roster. Inject types into it.
Optional desktop helper (not the phone roster): copy the user extension
```
cp -R plugins/aider-desk ~/.aider-desk/extensions/gbr-pair
```
from GrokBuildRemote-Agents/plugins/aider-desk. Tools: gbr-status, gbr-inject against http://127.0.0.1:8788 after gbr-agent run. This is a user install. Do not merge it into AiderDesk core.

Loopback inject is unauthenticated unless GBR_BOT_REQUIRE_KEY=1.

What fails (and why)

If you…	Phone sees
Expect AiderDesk Electron / PWA chat on the phone	Nothing — not a TTY. `gbr-agent` does not scrape Electron.
Treat `~/.aider-desk/extensions/gbr-pair` as a core AiderDesk feature	Wrong. User extension only. Unaffiliated. Not a hotovo core PR.
Paste live `curl \| bash` into Aider / AiderDesk docs	Mutable remote install. Pin v0.6.0 and checksum instead.
Point AiderDesk at `http://127.0.0.1:8788` as a chat	Bot API JSON. Not an Aider transcript.

Aider CLI in a terminal is the attach. AiderDesk is an optional user extension for desktop tools. Neither is an official Aider-AI or hotovo product of ours. Other repos should link /integrations, not copy install.sh.

Why Aider CLI, not AiderDesk core

Build Remote Agent’s native attach is inject into a terminal. Aider CLI is a TUI you run as aider. That is a window with a title, so it shows up on the roster. AiderDesk’s job is the desktop cockpit — keep it. Pairing helpers stay under the user’s ~/.aider-desk/extensions/gbr-pair. This page is a use case, not an Aider or AiderDesk adapter and not an endorsement.