Connect Codex and Claude

Three separate connectionsCopy Anchor Link

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.

CodexCopy Anchor Link

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.

ClaudeCopy Anchor Link

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 attentionCopy Anchor Link

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. Do not include login credentials, tokens, or private conversation text.

Instructions for a local agentCopy Anchor Link

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.