Test the apps you build with Bolt before you ship
Bolt prompts a full-stack app into a WebContainer, but the preview differs from production. Kane CLI drives your deployed Bolt app in a real browser, verifies it step by step, and returns a clean pass or fail. Free to install.
or read the documentation
Why test apps built with Bolt
Bolt, from StackBlitz, turns a prompt into a full-stack web app on WebContainers, deploying the frontend, backend, and database to Netlify or Vercel. That speed is why the deploy needs a second pair of eyes.
The WebContainer preview is more forgiving than production. The app can boot with undefined env vars, and Stripe or Supabase functions hit CORS and row-level-security 403s. The bug is three clicks deep on the live URL.
Kane CLI is that second pair of eyes, pointed at the deploy, not the sandbox. Describe the journey in plain English and it drives your live Bolt app in a real Chrome browser, showing where production diverges from preview.
What Kane CLI tests in your Bolt app
From a Supabase login to a full Stripe checkout, verified on the deployed URL in a real browser.
The deployed app, not the preview
Run your flows against the live Netlify or Vercel URL, not the WebContainer editor, to catch bugs that only appear once the app leaves StackBlitz.
Env vars and missing secrets
Bolt secrets do not always reach your host. Walk the real flow and catch screens that crash or render blank when a key lands undefined in production.
Supabase auth and RLS
Sign up, log in, and open a protected dashboard. Surface the row-level-security 403s and edge function CORS that pass in preview but fail live.
Stripe checkout after deploy
Bolt-generated Stripe code that calls the API fine in preview can break on CORS or webhook config in production. Walk the full purchase so it never reaches a customer.
Routing and hard-refresh
Client-side routes can 404 on a direct hit or refresh once deployed. Verify deep links, back-button, and reload across the app, not just first paint.
Console errors and dead network calls
Crawl the deployed app for console errors, failed fetches, and blank renders from a missing root or unhandled error, the kind the WebContainer hides.
Build up confidence before you ship
Start in your terminal
Validate on the cloud
Release with confidence
Built for the preview-to-production gap
Kane CLI and KaneAI share the same automation engine and dashboard.
From WebContainer preview to verified deploy
Bolt prompts the app into existence, Kane CLI proves the deploy works. Close the gap between a WebContainer preview and a verified production journey before you ship.
Verify the live deploy, not the sandbox
Point Kane CLI at your real Netlify or Vercel URL. It drives a true Chrome browser against production, so preview-only bugs in env vars, CORS, and routing surface where they bite.
Evidence you can share
Every run produces a persistent video, a step trace, and a replay link to drop into a PR, a bug report, or a message to your team.
Test your Bolt 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 Bolt project.
Deploy, then point at the live URL
Publish your Bolt app to Netlify or Vercel, then run flows against that production URL yourself or have Cursor or Claude Code run them for you.
Describe the flow and verify
Write the journey in plain English. 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
Deploy your Bolt project, point Kane CLI at the live URL, and describe the journey in plain English, for example "sign up, create a project, and confirm it shows on the dashboard." Kane CLI drives the deployed app in a real Chrome browser, checks each step, and returns a clean pass or fail with video evidence. The StackBlitz WebContainer preview behaves differently from your Netlify or Vercel deploy, so a flow that looks fine in the editor can break in production.
Bolt runs your app inside a StackBlitz WebContainer that is forgiving in ways production is not. Secrets set in Bolt do not always reach your host, so the deployed app boots with undefined env vars. Stripe and Supabase edge functions that worked in preview hit CORS or RLS 403 errors against real origins. Case-sensitive imports that pass on the WebContainer fail on a Linux build server. Kane CLI runs your real flows against the deployed URL, so you catch the preview-versus-production gap before a user does.
The deployed app on its real host, sign-up and login backed by Supabase or your auth provider, protected dashboard routes, forms that write to the database, Stripe checkout after deploy, client-side routing on hard refresh, and console errors or failed network calls that only appear outside the WebContainer preview. It checks each step, not just the final screen, and flags exactly where the app breaks.
Yes. If you pull your Bolt project into Cursor, Claude Code, Codex, or Gemini to keep iterating, point that agent at the guide at testmuai.com/kane-cli/agents.md. It installs Kane CLI, runs flows with the --agent flag, reads the structured results, and fixes what failed. Ship from Bolt, verify the deploy 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, 3 on timeout. Wire it into the Netlify or Vercel build connected to your Bolt project so every deploy runs your key flows against the live URL.
The CLI is free to install and use. Local runs are free; cloud runs on the TestMu AI grid bill against your TestMu AI plan. Start on the free tier and verify your deployed Bolt app end to end without a credit card.
Teach your agent to test what it builds
Pull your Bolt project into Cursor or Claude Code, point it at the Kane CLI guide, and it installs, authenticates, and verifies your deployed app in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md