Lovable: Agent Signs In to Test Login-Protected Pages
LovableLovable's browser testing agent can now sign into an app during testing and check pages that sit behind a login screen, such as dashboards and account pages, instead of stopping at the login wall. The feature requires the app's authentication to run on Lovable Cloud, its built-in backend, and Lovable automatically signs in as the app's sole user when there is only one, or asks in chat which account to use when there are several. Workspace admins and owners can also direct Lovable to sign in as a specific person, giving teams more control over what the agent tests.
Key Takeaways
- Lovable's testing agent can now sign into an app during automated browser testing to reach pages behind a login screen.
- The capability is limited to apps whose authentication runs on Lovable Cloud, the platform's built-in backend.
- For single-user apps, Lovable signs in automatically as that user without any extra setup.
- For multi-user apps, Lovable asks in chat which account to test with if none has been specified.
- Workspace admins and owners can pre-select a specific account for Lovable to sign in as.
- The update extends existing browser testing (navigation, form-filling, screenshots) to previously untestable authenticated pages like dashboards and account views.
Sources & Mentions
1 external resource covering this update
Testing What Used to Be Out of Reach
Lovable's automated browser testing previously hit a wall the moment it encountered a login screen: it could verify the public parts of an app, but anything gated behind authentication, dashboards, settings pages, account views, went untested. Lovable closed that gap by teaching its testing agent to sign in on the app's behalf and continue checking the pages behind the login.
How It Decides Who to Sign In As
The feature only works when an app's authentication runs on Lovable Cloud, the platform's built-in backend, since that is what lets Lovable manage credentials safely during a test run. From there, the behavior adapts to how many users the app has:
- If the app has exactly one user, Lovable signs in as that person automatically.
- If the app has multiple users and no preference has been stated, Lovable asks in chat which account to use before proceeding.
- Workspace admins and owners can skip that back-and-forth entirely by telling Lovable up front to sign in as a specific person.
Why It Matters
For apps built around accounts, subscriptions, or role-based access, most of the meaningful functionality lives behind the login screen. Extending automated testing there means Lovable can now catch broken dashboards, misconfigured permissions, or UI bugs on authenticated pages before a real user ever encounters them, rather than only validating the marketing page and sign-in flow. It is a natural extension of Lovable's existing browser testing, which already navigates pages, fills forms, and captures screenshots to catch issues automatically.