Authentication issues

Use this page to resolve problems with dashboard sign-in, email verification, two-factor authentication (2FA), CLI sign-in, and organization access. For 401 responses from the API, see Invalid API key.

You can’t sign in

Reset your password

To reset your password, follow these steps:

1. Open the Runtype Dashboard.
2. Enter your email address and click Continue.
3. Click Forgot password?, then follow the prompts to get a reset code by email.
4. Enter the code from the password reset email.
5. Set a new password.

Email address not recognized

If the sign-in form doesn’t recognize your email address, try these fixes:

• Check your email address for typos.
• If you signed up with Google, click Continue with Google instead of entering an email address and password.
• If you don’t have an account yet, create one.

Password rejected

If the sign-in form rejects your password, try these fixes:

• Check that Caps Lock is off.
• If you signed up with Google, click Continue with Google.
• If you don’t remember your password, reset it.

Account locked

Too many failed sign-in attempts lock your account for a period of time. The sign-in form tells you that your account is locked and when you can try again. After the lockout ends, sign in with your password or reset it. If you still can’t sign in, contact support.

Google sign-in issues

OAuth error after you select Google

If an OAuth error appears after you click Continue with Google, try these fixes, one at a time:

• Allow pop-ups for the Runtype Dashboard.
• Clear your browser cookies for the Runtype Dashboard.
• Open the Runtype Dashboard in a private browsing window.
• Use a different browser.

Wrong Google account

If you signed in with the wrong Google account, follow these steps:

1. At the bottom of the sidebar, click your account menu.
2. Click Log out.
3. In your browser, sign out of the Google account that you don’t want to use.
4. Open the Runtype Dashboard and click Continue with Google.
5. Select the correct Google account.

Email verification

You didn’t receive a verification email

If the verification email doesn’t arrive, check your spam or junk folder, and allow 5 to 10 minutes for delivery. If the email still doesn’t arrive, or the link in it expired, send a new verification email.

Send a new verification email

To send a new verification email, follow these steps:

1. Sign in to the Runtype Dashboard.
2. On the dashboard home, find the card titled Earn up to amount of build credit. If the card is collapsed, expand it.
3. Click Resend verification email. The message Verification email sent. Check your inbox. appears.
4. Open the link in the new verification email.

If the build credit card doesn’t appear, or the message Could not send. Verify from account settings in the sidebar. appears, verify your email address from your account settings. For the location, see Manage your sign-in settings.

Two-factor authentication

You lost your 2FA device

If you lost the device that generates your 2FA codes, sign in with one of your backup codes. If you don’t have a backup code, contact support.

After you sign in, set up 2FA again and save the new backup codes. For the location, see Manage your sign-in settings.

Your 2FA code doesn’t work

If the sign-in form rejects your 2FA code, try these fixes, one at a time:

• If you use an authenticator app, synchronize the time on your device.
• Wait for the next code and enter it.
• Enter a backup code instead.

Manage your sign-in settings

Your account settings hold your password, 2FA, backup codes, email addresses, and linked Google account.

To open your account settings, follow these steps:

1. At the bottom of the sidebar, click your account menu.
2. Click Account. Your account settings open.

When you turn on 2FA, save the backup codes in a secure location. You need them to sign in if you lose your 2FA device.

Session expired

If your session expires, sign in again.

A link opens a different page

If the notice That link couldn’t be used, so we’ve brought you here instead. appears when you open a link to the Runtype Dashboard, Runtype couldn’t open the page in the link and opened another page instead. Go to the page from the dashboard navigation, or ask the sender for a new link.

Organization access

Switch to another organization

To switch to another organization, follow these steps:

1. At the bottom of the sidebar, click your account menu.
2. Click Switch organization. The Switch Organization dialog opens.
3. Select the organization that you want to use.

Expected organization is missing

Only an organization admin can invite you to an organization. To join an organization, follow these steps:

1. Ask an organization admin to invite your email address. If you can’t find an earlier invitation email, ask the admin to invite you again. For the admin steps, see Team members and permissions.
2. Open the invitation email and click the invitation link. If you aren’t signed in, the Join your team page opens.
3. Sign in, or create an account if you don’t have one. Runtype opens the organization.

Workspace setup fails after you sign in

After you sign in, Runtype sets up your workspace. If setup fails, a Something went wrong screen shows one of these messages:

• We could not verify your account state. Your personal workspace remains hidden until this succeeds.
• We could not finish setting up your workspace. Try again.

To continue, click Try again. If you belong to an organization, or someone invited you to one, click Pick a workspace or Accept an invite, then select the organization.

If the dialog shows You don’t have any pending workspaces yet. Ask your admin to invite you, then sign back in., ask an organization admin to invite you. After they send the invitation, sign out and sign in again.

Browser sign-in fails for an MCP client or app

When you connect an MCP client or another app to your Runtype account, a browser window asks you to sign in and approve access. If an Authorization failed screen appears instead, use the following table to find the fix.

For the Runtype MCP server sign-in options, see Runtype MCP server.

CLI sign-in issues

If CLI commands fail with an authentication error, follow these steps:

1. To check whether the CLI is signed in, and which organization the current directory uses, run runtype auth status.
2. To remove the login that the current directory uses, run runtype auth logout.
3. To sign in again, run runtype auth login. A browser window opens with the Sign in to authenticate the CLI page.
4. Sign in to your Runtype account. The CLI stores your new credentials.

If a browser isn’t available, such as in a CI job, run runtype auth login --api-key YOUR_API_KEY. To create a key, see Managing API keys.

Contact support

If you still can’t sign in, contact Runtype support and include these details:

• The email address for your account.
• The date of your last successful sign-in, if you know it.
• The error messages or screenshots that you see.

Next steps

Use these pages to continue:

• Creating your account: create an account
• Team members and permissions: manage organization access
• Managing API keys: create and rotate API keys
• Authentication: authenticate API requests
• Common errors and solutions: troubleshoot other errors