Test the apps you build with Lovable before real users log in
Lovable builds a React and Supabase app from a prompt, but auth, RLS, and the deployed build often work for you and break for new signups. Point Kane CLI at your live Lovable app and verify the flow in a browser. Free to install.
or read the documentation
Why test apps built with Lovable
Lovable turns a prompt into a full-stack app: React frontend, Supabase database, auth, edge functions, and Stripe checkout. That speed is the point, but the generated backend only gets exercised once a second real user shows up.
That is where Lovable apps break. The auth listener can deadlock and freeze after login, RLS ships off or too permissive so a new signup sees nothing or everyone's data, and the app that works in preview goes blank on Vercel.
Kane CLI is the second pair of eyes. Describe the journey in plain English and it drives your live Lovable URL in a real Chrome browser, signs up fresh, and checks data isolation. Lovable syncs to GitHub, so your agent can run it.
What Kane CLI tests in your Lovable app
Supabase auth, RLS, and the deployed build, verified for a real second user.
Supabase auth for a fresh user
Sign up as a new account, confirm the redirect after login, and verify the session holds. This is where Lovable apps fail most: the onAuthStateChange listener that deadlocks and freezes the screen for everyone but you.
Row Level Security and data isolation
Create records as one user, log in as another, and confirm neither can see or write the other's data. Catch the missing or over-permissive RLS policy before an anon key dumps your table.
Generated CRUD and forms
Submit the forms Lovable wired to your Supabase tables, check validation, and confirm the row lands and reads back. Catch the silent insert that never reaches the database.
Stripe checkout and subscriptions
Walk the full purchase flow, upgrade and downgrade a plan, and confirm the webhook updated the user's tier, so a broken checkout never reaches a paying customer.
Deployed build, not just preview
Run against your Vercel or Netlify domain to catch the blank screen from a missing env var, a 404 on refresh from SPA routing, and asset chunks that 404 after a redeploy.
Regression after every reprompt
Lovable adds tables and rewrites components as you build, and the next prompt can quietly break a flow or skip RLS on a new table. Lock in known-good journeys and re-run them on every change.
Build up confidence before real users sign in
Start in your terminal
Validate on the cloud
Release with confidence
Built for the prompt-then-verify loop
Kane CLI and KaneAI share the same automation engine and dashboard.
Built for the prompt-then-verify loop
Lovable turns your prompt into a React and Supabase app in minutes. Kane CLI proves the generated auth, data, and checkout work for a real user before that app reaches anyone.
Verify the live app, not the code that looks right
Generated code reads correctly far more often than it runs correctly. You or your coding agent point Kane CLI at the live Lovable URL, and it drives the deployed app in a real browser to confirm the flow, not the screenshot.
Evidence you can share
Every run produces a persistent video, a step trace, and a replay link you can drop into a PR, a Lovable bug report, or a team message.
Test your Lovable app in three steps
Install Kane CLI
Run npm install -g @testmuai/kane-cli and sign in with your TestMu AI account. Nothing to wire into your Lovable project or Supabase schema.
Point it at your Lovable URL
Use the Lovable preview link or your deployed Vercel or Netlify domain. Run flows from the terminal, or tell Cursor, Claude Code, or Codex to run them against the synced GitHub repo.
Describe the flow and verify
Write the journey in plain English: sign up, create a record, confirm it is isolated to that user. Kane CLI drives a real browser, verifies each step, and returns a pass or fail with evidence.
Get Started With Kane CLI
🎉 Launch offer: Bonus credits for the first 3 months on paid plans
Choose the right plan for you
Local test authoring via CLI
Auto-heal & vision
View test cases on UI
Test Manager
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Choose the right plan for you
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Get the technical rundown
Documentation
Everything you need to install, configure, and run Kane CLI in under 2 minutes.
Frequently asked questions
Install Kane CLI, then describe the journey in plain English, for example "open the published app, sign up as a new user, create a record, and confirm it shows on the dashboard." Kane CLI drives your live Lovable URL in a real Chrome browser, signs in through Supabase auth, checks each step, and returns a pass or fail with video evidence. Run it from the terminal against the Lovable preview or your deployed domain, or let your AI coding agent run it after editing the synced GitHub repo.
Lovable generates the React frontend, Supabase backend, database, and auth wiring from a prompt, and most of that logic only fails once a second user logs in. The classic break: an app that works for you but errors for a fresh signup because Row Level Security policies are missing or too permissive, or because the generated onAuthStateChange listener makes a database call that deadlocks and freezes the screen after login. Add the preview-works-but-deploy-shows-blank traps from missing env vars and SPA routing, and clicking by hand is not enough. Kane CLI verifies the real flow in a browser, as a real user, before you ship.
The full Supabase auth journey for a new user, create-read-update-delete on your generated tables, multi-user data isolation so one account cannot see another's records, Stripe checkout and subscription tier changes, and the deployed build rendering instead of a blank screen. It also catches SPA 404s on refresh, console errors, and broken API or edge-function calls. It checks each step, not just the final screen, and flags the exact point where the app breaks.
Yes. Lovable syncs your codebase to GitHub, so a coding agent like Cursor, Claude Code, or Codex can take over and edit it. Point that agent at the guide at testmuai.com/kane-cli/agents.md and it will install Kane CLI, run flows with the --agent flag, read the structured results, and fix the failing RLS policy or broken form before you see it. Generate with Lovable, hand off to your agent, verify with Kane CLI, in one loop.
Yes. Authenticate with your TestMu AI credentials, pass --headless and --timeout, and gate your pipeline on the exit code: 0 on pass, 1 on fail, 2 on setup or auth errors, and 3 on timeout. Run your signup, data-isolation, and checkout flows on every Vercel or Netlify deploy, so a missing env var or broken redirect never reaches production.
The CLI is free to install and use. Local runs are free; cloud runs on the TestMu AI grid are billed against your TestMu AI plan. Start on the free tier and verify your Lovable app end to end without a credit card.
Teach your agent to test what Lovable builds
Lovable syncs your app to GitHub. Point your coding agent at the Kane CLI guide and it will install, authenticate, and verify the signup, RLS, and checkout flows in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md