ClawDad · Guide

Install and pair your phone

Check phone beta availability, install through the approved store route, and scan a fresh pairing code.

Check availability first

Open Setup in your tester portal. Phone access shows a device link when one has been configured. Admission to the website beta reserves a place; phone testing also depends on the appropriate store build and invitation.

iPhone and TestFlight

Install Apple's TestFlight app. Use the external TestFlight invitation or approved testing link supplied for your admitted beta place. Accept it in TestFlight and install the available ClawDad build.

An internal TestFlight build is limited to its App Store Connect team and does not establish access for an external tester. If TestFlight says no build is available, the invitation is missing, or the link is not shown in your portal, phone installation is still pending. You can prepare your computer while Cody resolves external build availability. Do not join an Apple developer team just to install the external beta.

Android

Use the Google Play testing opt-in/install link when it appears for your device. The Google account used by Play may differ from your portal email; give Cody the intended testing email through the private portal when requested. A desktop download does not install the phone app. If no Android link is available, phone installation is pending.

Pair with your computer

  1. Keep ClawDad running on the computer you want to use.
  2. On Mac, open Settings → Device Pairing → Allow a Device to display a fresh QR code. Pair your phone in the setup checklist opens Device Pairing. On Windows, use the computer app's device-pairing control; its labels may differ by build.
  3. On the iPhone Home screen, choose Add Computer to open the scanner titled Pair iPhone. On Android, use the pairing scanner available in your installed beta build. Allow camera access if requested.
  4. Scan the QR directly from your computer. Confirm that the connected computer is the one you intended.
  5. Select a project and conversation. Send a short request to verify the connection.

Pairing codes and screenshots of them are private. If a code has expired, generate a fresh one. Check camera permissions if scanning is unavailable. Keep the host computer awake and online for remote use.

First checks

Open an existing conversation, send a short message, and confirm the result appears on both devices. Switch projects, return with the visible Back control, and reopen the conversation. Verify the selected provider/account after switching accounts.

Use Direct to send into the current conversation; during active work it is considered after the current tool call. Use Queue to wait for the active turn to finish before beginning the next one.

Testers should report differences between iPhone, Android, Mac, and Windows with the exact build and host/phone combination. A feature shown on one combination may still be pending on another during the beta.

Guide reviewed October 26, 2026. Check the tester portal for current build availability.