BOTLOBBIESWhy can the website ask for an email code on a different browser?
A confirmed website account can be asked for an email code when the browser is not recognized as trusted. The password and the browser-trust check are separate, and a different browser may not have the same saved cookie.
Treat browser trust as local to that browser
The service records a trusted-browser token through a cookie rather than treating every device using the same person or connection as permanently recognized. Signing in on a phone does not automatically copy that cookie to a desktop browser. Clearing browser data or using a separate browser profile can therefore result in another code step. This is a website account check, not a request to repeat Epic linking, transfer your bot to another owner, or purchase a second subscription before you can return to the panel.
Use the challenge shown by the current login
When the website presents a code screen, use the message for that particular sign-in and complete the displayed flow. Entering a correct password does not mean the session is already open if the page is still asking for its code. A sending limit can produce a wait message, so repeated attempts are not always useful. If the code does not appear, check the inbox hint and folders and use the offered resend controls instead of requesting several unrelated recovery emails from different tabs.
Expect old trust to stop after a password change
A trusted browser is not an exemption from changing account credentials. The service associates newer trusted-device records with the password version they were authorized under, and a later password change can invalidate older trust. If you have just reset the website password, a fresh sign-in or email-code check may be expected. Keep your recovery inbox under your own control and avoid treating a remembered browser as a reason to share the password. If the check repeats unexpectedly, describe the browser and action without sending cookies or codes.