FAQ: New Login Experience with SSO Support

Last updated: August 18, 2025

πŸ” FAQ: New Login Experience with SSO Support

We’ve upgraded our login experience to improve security, compliance, and ease of access β€” especially for enterprise teams. Below are answers to common questions to help you navigate the transition.


πŸ”„ What changed with the login system?

We've moved away from personal token-based logins. Starting with this release, users now sign in using one of the following secure authentication methods:

  • βœ… Google SSO

  • βœ… GitHub SSO

  • πŸ“¨ Email + Password


πŸ” Why was this change made?

This update brings our login system in line with industry best practices, offering:

  • Stronger security through SSO and password-based authentication

  • Simplified access management

  • Improved compliance with modern security frameworks

  • Elimination of personal tokens, which are harder to manage securely


πŸ‘₯ Who is affected?

All users will be affected by this update. Once you install the new version, you’ll be automatically logged out and prompted to sign in again using one of the new login methods.


πŸ“§ What email should I use to log in?

Make sure to use the same email address that was previously associated with your personal token. This ensures your project data, preferences, and access permissions carry over correctly.


πŸ’Ύ Will I lose any of my data or projects?

No β€” all your projects, data, and settings are preserved. Only the authentication method has changed.


πŸ§ͺ What if I was using a personal token before?

Personal tokens are no longer supported. You should:

  • Use SSO or email/password to log in going forward.

  • If you were using a token in scripts or tools, refer to updated authentication instructions or reach out to support.


πŸ†˜ What if I can’t log in or forgot which email I used?

If you're unsure about your login email or run into access issues:

  1. Try logging in using the email tied to your previous token.

  2. Reach out to our support team at support@autonomyai.io for help.


βš™ Do I need to update anything on my end?

Just log in again when prompted. If you previously used a personal token for login, select one of the new methods (SSO or email/password) going forward.


πŸ“₯ Why am I seeing multiple popups during SSO login?

Whether you're signing in with Google, GitHub, or email/password, your login is handled securely in your browser. As part of this flow, you may see up to three system prompts from VS Code or your browser. These are expected and safe:

1. External Website Confirmation (from VS Code)

Popup Text: β€œDo you want Code to open the external website?”

βœ… Click Open to launch your browser and begin secure login.

This is required for OAuth to connect you with your identity provider.

2. Open Visual Studio Code (from Browser)

Popup Text: β€œOpen Visual Studio Code?”

βœ… Approve this to return from the browser back to VS Code after you log in.

It ensures the extension receives your authentication securely.

3. URI Handler Permission (from VS Code)

Popup Text: β€œAllow β€˜Autonomy.AI’ extension to open this URI?”

βœ… Click Allow to complete the login flow in the Fei plugin.

This confirms that VS Code can handle secure login links (like vscode://...).