Sign in and recover your account
3 minute read · Cloud & Sync
Your Vortex account owns your cloud resources. It is separate from the coding-agent account you connect to build an app.
- Sign in and finish the requested steps
- Recover the right thing
- Follow the right recovery path
- Verify an account change
Sign in and finish the requested steps
Register or sign in through the account screen. Complete email verification when requested. If two-factor authentication is enabled, use its challenge or an available recovery code. Connecting a coding provider does not complete these Vortex account steps for you.
If a verification email does not arrive, check the address and spam folder, then use the supported resend control. A mail-delivery error means the request needs attention; do not repeatedly create accounts to work around it.
Recover the right thing
Use password recovery to request account-reset mail and submit its reset token. Two-factor enrollment and recovery-code regeneration have separate account controls. Keep recovery material in a safe place.
Your account password and Vault unlock are different concerns. Resetting a login password is not permission to replace an unreadable encryption key. Follow the Vault recovery guide when you can sign in but cannot unlock saved work.
Changing accounts changes the local data scope. Old account results and approvals must not appear in the new account. Report a mismatch with the account state and operation, without sending credentials. See support.
Follow the right recovery path
| What you see | What to do | What this restores |
|---|---|---|
| Password rejected | Use password reset from sign-in, open the newest recovery email and submit its token through the supported account screen. | Access to the Vortex account; it does not replace a lost Vault key. |
| Email verification required | Open the verification message for this account. Finish the browser-to-app handoff, then refresh account status. | Verified account access after the server accepts the token. |
| Two-factor challenge | Use the enrolled authenticator or an unused recovery code. | This sign-in challenge; recovery codes must be kept private. |
| Signed in, Vault locked | Continue to Vault unlock or its own recovery flow. | Access to encrypted resources, using the correct existing key. |
Use the newest requested email link and the same account that requested it. If the link opens a browser but Vortex does not open, use the page's explicit Open Vortex action and allow the OS handoff. Do not paste a recovery URL into an agent conversation: it may contain an account token.
Verify an account change
Before switching accounts, let important local saves finish and note any sync conflict. Sign out using the account controls, then sign in to the intended account. Check its workspace list before opening a saved connection. A missing workspace may mean a different account or a locked Vault; it is not a reason to create a replacement over an existing checkout.
When reporting a sign-in failure, include the step, time, app version and visible error. For an invalid server response, mention whether a browser page appeared where account JSON was expected. Keep passwords, two-factor codes and full recovery links out of screenshots. See Vault recovery for the separate encrypted-data boundary.