Lovable: Generated Login Pages Now Include Sign in with Lovable by Default
LovableLogin pages that Lovable builds for apps using Lovable Cloud now include Sign in with Lovable by default, next to email and password and Google sign-in. App users can sign in with their Lovable account, and Lovable registers the sign-in for the project automatically with nothing to configure. Builders who want a different mix of methods can name them in the prompt, and these sign-ins consume no credits.
Key Takeaways
- Lovable-generated login pages for Lovable Cloud apps now include Sign in with Lovable by default.
- It appears alongside email and password and Google sign-in, rather than replacing them.
- Lovable registers the sign-in for the project automatically, so there is nothing to configure.
- Builders can override the defaults by naming the sign-in methods they want in the prompt.
- Sign-ins consume no credits, so the option adds no credit cost.
- It follows the previous day's launch of Lovable-account sign-in for Cloud apps, turning an opt-in feature into the default.
Sign in with Lovable becomes a default login method
Lovable changed what it generates when a builder asks for a login page in an app that uses Lovable Cloud. Those pages now include Sign in with Lovable by default, alongside the existing email and password option and Google sign-in. Previously the Lovable-account option had to be switched on deliberately, either in the project's auth settings or by asking in the chat.
Zero configuration
Lovable registers the sign-in for the project on its own. There are no client IDs to create and nothing to paste in. When a user chooses the button, they authenticate with their Lovable account, and the app receives the profile details the sign-in provides, such as name, email address, and profile picture. This builds on the capability Lovable introduced a day earlier, which let Cloud apps accept Lovable accounts and keeps the sign-in current when the app's address changes.
Staying in control of sign-in methods
The default is only a starting point. A builder who wants a different set of methods can name them in the prompt, for example asking for email and password only, or Google sign-in only, and Lovable will generate the login page accordingly.
Cost
Sign-ins through this method consume no credits, so offering it does not add to a project's credit usage.
Why it matters
For many prototypes and internal tools, the first real users are people who already have Lovable accounts, such as teammates and testers. Making the option appear automatically removes a setup step and gives those users a one-click way in, while still leaving the choice of methods to the builder.