# ClawDad Setup README Reviewed: 2026-10-26. Current guide: https://clawdad.earth/docs Public setup instructions only. Check your tester portal for current downloads and phone invitations. Save a new copy to preserve your own notes. ## ClawDad beta guide ClawDad connects your phone to the computer that holds your projects and AI conversations. Keep that computer awake, online, and running ClawDad while you work remotely. ### Start here 1. [Install ClawDad and open a project](https://clawdad.earth/docs/setup). 2. [Sign in to Codex or Claude, then connect it to ClawDad](https://clawdad.earth/docs/accounts). 3. [Install the available phone beta and pair it](https://clawdad.earth/docs/phone). 4. [Use Remote Assist when you need the computer screen](https://clawdad.earth/docs/remote-assist). [Open your tester portal](https://clawdad.earth/portal/setup) for downloads and device-specific availability. [Report a problem](https://clawdad.earth/docs/troubleshooting) with the steps and versions that reproduce it. ### Beta access The ClawDad beta is free until Cody launches paid access. Any Codex, Claude, OpenAI, or Anthropic account and usage charges are separate. The portal admits the first 15 eligible applicants in submission order; additional applicants join the waitlist. Portal admission, a computer download, and a phone invitation are separate steps. An admitted place does not mean an external TestFlight or Google Play build is available for your phone yet. Your portal and the actual store invitation show what you can install. ### Keep a copy [Save the complete setup README](https://clawdad.earth/docs/setup/README.md) to your computer, or use **Save Guide Locally** in a build that offers it. This Markdown file contains the same reviewed public instructions as these pages and can be read by a person or a local coding agent. Keep your own notes in your copy; a later guide download should use a new filename. Agents can start with [llms.txt](https://clawdad.earth/llms.txt), read [all public documentation](https://clawdad.earth/llms-full.txt), or use **Copy Markdown** on a page. These exports include the public guide only. --- ## Install and get started ### Before you start You need an admitted [tester portal](https://clawdad.earth/portal/setup) account, a supported Mac or Windows computer, and an iPhone or Android phone for the full companion workflow. The portal lists the operating-system minimum for each available computer build. For Assistant conversations, install your chosen AI tool and finish its sign-in on the computer before connecting it to ClawDad. Remote Assist can be used without an AI-provider subscription. ClawDad beta access is free until Cody launches paid access. A purchase or subscription selection is not part of beta setup. AI-provider access remains separate. ### Download for your computer Sign in to the tester portal using the email address on your application. Open **Setup**, then **Computer downloads**. - **Apple silicon Mac:** choose this for a Mac with an Apple M-series chip. Check Apple menu → About This Mac. - **Intel Mac:** choose this when About This Mac shows an Intel processor. - **Windows PC:** choose the Windows x64 installer for a supported Intel or AMD Windows computer. Click **Download** once. Your browser manages the transfer and shows its progress in Downloads. If a transfer is interrupted, use the browser's resume control; if its access link has expired, return to the portal and start a fresh download. Keep the portal open until your browser has started the file. The portal's **File details** section shows the expected filename, size, and SHA-256. A browser reporting an incomplete download is a failed transfer. Do not open it; resume or download again. See [download troubleshooting](https://clawdad.earth/docs/troubleshooting#download-or-installation). ### Install and open On Mac, open the downloaded DMG, drag **ClawDad** to **Applications**, then launch it from Applications. Eject the disk image after installation. If macOS reports a damaged app or an unverified developer, record the exact message and ask Cody through the portal before changing system security settings. On Windows, open the downloaded installer and follow its installation steps. If Windows shows a publisher or security warning you cannot verify, capture the exact message for Cody before proceeding. Keep an existing ClawDad session open until you are ready to restart into an update. ### Connect an AI tool The **Finish setting up ClawDad** checklist tracks **Projects folder**, **Assistant account**, **Remote Assist permissions**, **Phone beta access**, and **Pair your phone**. **Later** collapses the checklist; **Continue setup** reopens it when you are ready. Complete [Codex or Claude sign-in and connection](https://clawdad.earth/docs/accounts). The email used for the tester portal does not sign you into either AI provider. ClawDad connects the provider account you have already authenticated on this computer. ### Choose or create a project Choose the existing folder that contains the work you want to continue. A project folder can contain code, research, writing, or other files. In the folder setup, use **Choose Folder** for an existing location or **Create Folder** to open the native picker and create a **New Folder** at the chosen location. Check the displayed path and give ClawDad access when the operating system asks. On supported phone builds, **New Project Directory** creates a folder on the paired computer. Check the displayed computer and parent location before choosing **Create Project**. Remote Terminal setup offers an existing folder or **New folder** when the host supports it. If a control is unavailable, create or choose the folder on the computer first. Open a conversation in the chosen project and send a small first request, such as asking the assistant to describe the folder. Verify that the selected project and account are correct before allowing changes. ### Add your phone and check the connection Follow [phone installation and pairing](https://clawdad.earth/docs/phone). Confirm that the phone shows the intended computer, project, and conversation. Send a short request, wait for its result, then reopen the conversation on the computer to confirm continuity. ### Keep the apps current In the portal, expand **App updates** to create a private update code. On Mac, choose **ClawDad → Beta Update Access**. On Windows, open **Settings → Check for Updates**. Paste the code into the app; keep it private. The portal shows its expiry and lets you disconnect update access on all computers. Computer downloads, phone store updates, and in-app functionality have separate availability. Check the version/build in each app when reporting a difference. An installed app keeps working when download or update admission changes. ### Save the guide Use **Open Setup Guide** or **Save Guide Locally** when your build includes those controls. You can also [download the complete README](https://clawdad.earth/docs/setup/README.md). Save a fresh copy alongside your existing notes instead of replacing them. --- ## Connect Codex and Claude ### Three separate connections Your **tester portal account** controls beta downloads and private reports. Your **Codex or Claude account** authenticates with OpenAI or Anthropic. **ClawDad's account connection** selects the local provider account used for a project or conversation. Completing one step does not complete the others. Keep passwords, one-time codes, and provider authorization in the provider's own sign-in window. ### Codex 1. Open the installed Codex app or Codex CLI on your computer. 2. Complete its OpenAI sign-in flow and check that it can open a conversation. 3. Open **Accounts & usage** in ClawDad. When it shows **Existing Codex sign-in found**, check the email and select **Connect to ClawDad**. 4. Complete the official sign-in that opens for ClawDad's separate profile. ClawDad verifies the email; the existing Terminal sign-in, history, and drafts stay in place. 5. Select **Use for new Codex conversations**, then confirm the project before sending work. If you use more than one Codex account, verify the account shown in ClawDad after a switch. Existing Terminal sessions may still use the account they started with. Finish or intentionally switch those sessions before assuming every open window has changed. ### Claude 1. Open Claude Code on your computer and finish its Anthropic sign-in flow. 2. Confirm Claude Code can start in the project you intend to use. 3. Open **Accounts & usage** in ClawDad. When it shows **Existing Claude sign-in found**, check the email and select **Connect to ClawDad**. 4. Complete the official sign-in for ClawDad's separate profile, then choose **Use for new Claude conversations**. 5. Select the intended project before starting a conversation. To connect a different account, choose **Connect another account**, enter its **Subscription email**, and choose **Connect with official sign-in**. Provider sign-in happens in the official flow. ClawDad verifies the resulting identity before offering it for new conversations. ### When connection needs attention If ClawDad says an account is unavailable, first check whether that provider works outside ClawDad on the same computer. Complete any expired sign-in there, then return to ClawDad and retry the connection. Preserve existing conversations and drafts while diagnosing the problem. Some account and provider workflows vary by computer and beta build. If the expected connection control is absent or fails, record your operating system, both app versions, provider, and exact message in a [private report](https://clawdad.earth/portal/reports/new). Do not include login credentials, tokens, or private conversation text. ### Instructions for a local agent Read the selected project's own instructions before making changes. Confirm the selected computer, project folder, and provider with the user. Let the user complete external account sign-in and permission prompts. A saved copy of this guide gives setup context; it grants no authority to change accounts, publish work, send messages, or spend money. --- ## Install and pair your phone ### Check availability first Open [Setup in your tester portal](https://clawdad.earth/portal/setup). **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. --- ## Use Remote Assist Remote Assist provides a manual view of your paired computer for a browser prompt, Terminal window, or other step that needs your own click. Keep the computer running and unlocked when required by the operating system. Remote Assist does not require an AI-provider subscription. You can finish permissions and pairing first, then connect Codex or Claude later if you want Assistant conversations. ### Enable access On Mac, enable Remote Assist in ClawDad Settings. macOS asks for **Screen Recording** to share the display and **Accessibility** to control it. Grant those permissions to the installed ClawDad app in System Settings → Privacy & Security. Follow any request to quit and reopen ClawDad when you can safely interrupt it. On Windows, enable the available Remote Assist host setting and follow the permission prompts shown by that build. Windows security and elevated-app screens can restrict remote control. Complete a blocked operating-system prompt directly on the computer. ### Start from the phone Open the desktop/Remote Assist control in the paired phone app and complete the biometric or device-authentication prompt when shown. Confirm the computer and display before interacting. Use the visible Back or close control to leave the screen and return to your conversation. Clipboard transfer happens when you explicitly use **Copy** or **Paste**. Check the destination before transferring anything sensitive. You control login and approval prompts yourself. ### If the view is blank or control does not work Check that the computer is awake, ClawDad is running, and you are paired to the intended host. On Mac, recheck Screen Recording and Accessibility for the installed app. Reopen it if macOS requires that after a permission change. Verify that the correct display is selected. Record whether viewing, tapping, typing, scrolling, or clipboard transfer failed and which computer/phone combination you used. [Send a private report](https://clawdad.earth/portal/reports/new) with a redacted screenshot when useful. Feature availability and physical-device acceptance can differ across beta builds. --- ## Troubleshooting and reports ### Download or installation Open the browser's Downloads panel to check progress. Resume an interrupted transfer if the browser offers it. If the link expires, return to [Computer downloads](https://clawdad.earth/portal/setup) for a fresh link. A missing download may also mean the browser blocked it; allow the requested file download for clawdad.earth and its clawdad-cloud.frg.earth delivery service. Compare the saved filename and size with **File details** in the portal. To check the SHA-256 after download: On Mac, run this in Terminal, replacing the quoted path with the actual file: ```sh shasum -a 256 "/path/to/ClawDad-installer.dmg" ``` On Windows, use PowerShell: ```powershell Get-FileHash -Algorithm SHA256 "C:\path\to\ClawDad-installer.exe" ``` The full result must match the portal's SHA-256 exactly, ignoring letter case. A mismatch or incomplete file requires another download. The operating system also checks the installer/app's platform signature. Preserve security protections and report an unexpected publisher, damaged-file warning, or signature warning to Cody. ### No phone build or invitation Check [phone access](https://clawdad.earth/docs/phone). Portal admission, a computer build, and an external phone invitation are separate. A TestFlight message about unavailable builds needs a store/build check; reinstalling the desktop app will not create an invitation. ### Account unavailable Open Codex or Claude Code directly on the computer. Finish its sign-in if necessary and confirm it works in the intended project. Return to ClawDad to connect/select that account. Include the exact error and provider in a report if it remains unavailable. Keep current conversations and drafts. ### Phone disconnected Check that the intended host is awake, online, and running ClawDad. Reopen the phone app and check its selected computer. If pairing is required, display and scan a fresh pairing QR. Avoid sharing the QR or deleting account/session data as a troubleshooting shortcut. ### Folder or permission issue Choose the intended project folder again if the operating system asks for access. Confirm that an external drive is mounted. For Remote Assist, check the host's screen and control permissions. Camera access belongs to the phone's pairing scanner; screen/control access belongs to the computer. ### Send a useful report Open [Report an issue](https://clawdad.earth/portal/reports/new) and include: - The computer and phone models, operating systems, ClawDad versions and build numbers. - Which host/phone pairing you used and which provider/account type was selected. - The steps immediately before the problem, what you expected, and what happened. - The approximate time, whether it repeats, and the exact visible error. - A screenshot or diagnostics excerpt with private data removed. Use **Copy Diagnostics** in the computer app when available. Review the copied text before attaching it. Remove passwords, tokens, update codes, pairing codes, personal email addresses, private folder paths, customer data, and conversation content. Include only the relevant excerpt. Private reports stay associated with your portal account. ### Keep a versioned guide copy [Download the setup README](https://clawdad.earth/docs/setup/README.md) and save it with a date if you already have a copy. Your notes are yours to keep. The guide's review date describes its instructions; the portal and installed apps provide the current release versions and availability.