Skip to content

Add Build Remote Agent phone pairing (gbr/1) - #607

Open
LinespottingPrivate wants to merge 2 commits into
warpdotdev:mainfrom
LinespottingPrivate:feat/gbr-pair
Open

Add Build Remote Agent phone pairing (gbr/1)#607
LinespottingPrivate wants to merge 2 commits into
warpdotdev:mainfrom
LinespottingPrivate:feat/gbr-pair

Conversation

@LinespottingPrivate

Copy link
Copy Markdown

What

How-to page for pairing a phone running Build Remote Agent to a Warp session. Contrasts with Warp Remote Control (cloud publish/steer): GBR stays loopback (gbr-agent pair / run, attach :8788 or gbr-mcp).

Files:

  • src/content/docs/guides/external-tools/how-to-set-up-gbr.mdx
  • one nav row in src/sidebar.ts

How

curl -fsSL https://grokbuildremote.com/install.sh | bash
gbr-agent version          # v0.6.0+
gbr-agent pair && gbr-agent run
curl -sS http://127.0.0.1:8788/health

Phone is spectator + veto. Protocol gbr/1. Independent product by Linespotting AB. Not affiliated with xAI or SpaceX. No mailbox keys.

@cla-bot

cla-bot Bot commented Aug 23, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @LinespottingPrivate on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

@vercel

vercel Bot commented Aug 23, 2026

Copy link
Copy Markdown

@LinespottingPrivate is attempting to deploy a commit to the warpdotdev Team on Vercel.

A member of the Team first needs to authorize it.

@warp-for-oss

warp-for-oss Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

@LinespottingPrivate

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LinespottingPrivate

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@cla-bot

cla-bot Bot commented Aug 23, 2026

Copy link
Copy Markdown

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @LinespottingPrivate on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant