Test the apps you build with Firebase Studio before real users sign in
Firebase Studio and Gemini build a full-stack app from a prompt, but auth, security rules, and the deployed Hosting build often work for you and break for new signups. Point Kane CLI at your live app and verify the flow in a browser. Free to install.
or read the documentation
Why test apps built with Firebase Studio
Firebase Studio uses Gemini to turn a prompt into a full-stack app: the frontend, a Firestore database, Firebase Auth, Cloud Functions, and Hosting. That speed is the point, but the generated backend only gets exercised once a second real user shows up.
That is where these apps break. The auth flow works for your account but errors for a fresh signup, security rules ship in test mode or too permissive so a new user sees everyone's data, and the app that works in preview goes blank on Firebase Hosting.
Kane CLI is the second pair of eyes. Describe the journey in plain English and it drives your live Firebase Hosting URL in a real Chrome browser, signs up fresh, and checks data isolation. Re-prompt in Firebase Studio, then let your agent re-run it.
What Kane CLI tests in your Firebase Studio app
Firebase Auth, Firestore security rules, and the deployed build, verified for a real second user.
Firebase Auth signup for a brand-new user
Kane CLI registers a fresh account through Firebase Auth, follows the post-login redirect, and confirms the session survives a reload. This is where Firebase Studio apps break first: an auth flow that passes for you and falls over for the second real signup.
Firestore security rules and data isolation
It creates documents as one signed-in user, then signs in as another and tries to read them. If a Firestore rule shipped in test mode or too permissive, one Firebase Studio account can dump another's collection, and Kane CLI surfaces it before launch.
Generated forms write to Firestore
It fills the forms Firebase Studio wired to your collections, checks the validation Gemini generated, and reads the document back to prove the write actually reached Firestore instead of failing silently.
Live Hosting build, not the Studio preview
It runs against your deployed Firebase Hosting domain to catch the blank page from a missing runtime config, the 404 on refresh from SPA routing, and asset chunks that go missing after a redeploy.
Cloud Functions and backend data flows
It walks the actions that trigger Cloud Functions and backend writes, then confirms Firestore updated and the UI reflects it, so a broken function or skipped rule never lands in front of a real user.
Regression after every Firebase Studio reprompt
Each Gemini reprompt can add a collection or rewrite a component and quietly skip rules on the new path. Save your known-good Firebase journeys and replay them after every change to catch what the latest prompt broke.
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.
From Gemini prompt to verified flow
Firebase Studio turns one prompt into a frontend, Firestore, Firebase Auth, and Hosting. Kane CLI closes the loop by signing up as a fresh user and proving that generated stack actually holds before anyone else touches it.
Test the deployed Hosting app, not the preview that looked fine
A Firebase Studio preview can pass while the live Hosting build goes blank on a missing config value. Point Kane CLI at your deployed domain and it drives the real app in Chrome, so you trust the running flow over a clean-looking generation.
Proof for every reprompt
Each run leaves a video, a step trace, and a replay link tied to the exact Firebase journey, so you can show a teammate the security rule that broke or attach the passing signup flow to a PR.
Test your Firebase Studio app in three steps
Install Kane CLI
Run npm install -g @testmuai/kane-cli and sign in with your TestMu AI account. Nothing to add to your Firebase Studio project, Firestore schema, or security rules.
Point it at your Firebase URL
Use the Firebase Studio preview link or your deployed Firebase Hosting domain. Run flows from the terminal, or tell Cursor, Claude Code, or Codex to run them after each reprompt.
Describe the flow and verify
Write the Firebase journey in plain English: sign up a new user, create a record, confirm Firestore rules keep it isolated to that account. Each step is checked in a real browser, with a pass or fail and a shareable replay.
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 deployed app, sign up as a new user, create a record, and confirm it shows on the dashboard." Kane CLI drives your live Firebase Hosting URL in a real Chrome browser, signs up through Firebase Auth, checks each step, and returns a pass or fail with video evidence. Run it from the terminal against the Firebase Studio preview or your deployed Hosting domain, or let your AI coding agent run it after re-prompting in Firebase Studio.
Firebase Studio uses Gemini to generate the frontend, Firestore database, Firebase Auth, and Hosting config from a prompt, and most of that logic only fails once a second user signs in. The classic break: an app that works for you but errors for a fresh signup because Firestore security rules are missing, left in test mode, or too permissive, so one account can read another's data. Add the preview-works-but-deployed-Hosting-shows-blank traps from missing config 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.
It covers the parts of a Firebase Studio build that fail quietly: the full Firebase Auth signup journey for a new user, create-read-update-delete across your Firestore collections, and multi-user isolation so one account cannot open another's documents. It exercises your Firestore security rules from the browser, confirms the deployed Hosting build renders instead of going blank, and catches SPA 404s on refresh, console errors, and broken Cloud Function calls. Every step is checked, not just the final screen, so you get the exact point where the generated app breaks.
Yes. Once Gemini and Firebase Studio finish a reprompt, a coding agent like Cursor, Claude Code, or Codex can take it from there. Point the agent at the guide at testmuai.com/kane-cli/agents.md and it installs Kane CLI, runs the flows with the --agent flag, reads the structured results, and patches the failing Firestore rule or broken signup form before you ever see it. Reprompt in Firebase Studio, hand off, verify with Kane CLI, all in one loop.
Yes. Authenticate with your TestMu AI credentials, pass --headless and --timeout, and gate the pipeline on the exit code: 0 on pass, 1 on fail, 2 on setup or auth errors, and 3 on timeout. Wire your Firebase Auth signup, data-isolation, and Firestore CRUD flows into the job that runs on every Hosting deploy, so a missing config value or a loosened security rule 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 the signup, security rules, and data flows in your Firebase Studio app end to end without a credit card.
Teach your agent to test what Firebase Studio builds
Re-prompt in Firebase Studio, then point your coding agent at the Kane CLI guide and it will install, authenticate, and verify the signup, security rules, and data flows in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md