Test the apps the Replit Agent deploys before they reach users
The Replit Agent ships a full-stack app fast, but code that runs in the workspace can break on deploy. Kane CLI drives your deployed Replit app in a real browser and verifies each step in plain English. Free to install.
or read the documentation
Why test apps built with Replit
The Replit Agent turns a prompt into a full-stack app fast: it picks the stack, runs migrations, wires built-in auth, connects 160+ services, and deploys to a live URL. That speed is exactly why the deployed app needs a check.
The signature Replit bug is "works in the editor, breaks on deploy." A Secret missing from the live environment lets a form report success while the row never reaches Postgres, or an API route returns a 500 in production.
Kane CLI is that check. Describe the journey in plain English and it opens your live Replit URL in a real Chrome browser, walks each step, and confirms the result, no selectors. Save the flows and re-run to catch regressions.
What Kane CLI tests in your Replit app
From a single saved record to a full payment flow, verified on the deployed app.
The deployed app, not the editor preview
Replit bugs hide between the workspace and the live deployment. Kane CLI opens your deployed URL in a real Chrome browser and verifies the app users actually get.
Forms that look saved but never persist
A missing Secret or a 500 on an API route lets a form report success while no row lands in Postgres. Kane CLI submits the form, then confirms the record really shows up.
Replit built-in auth and protected routes
Sign up, log in, and check that sessions hold and protected pages gate correctly, the auth the Agent wired by hand and most likely to break on a later prompt.
Dashboards, CRUD, and internal tools
Create, read, update, and delete across the screens the Agent generated, and confirm the dashboard reflects the data, not an empty state or stale cache after a refresh.
Payments and connector-backed flows
When the Agent wires Stripe or one of its 160+ connectors, a key missing from the deployed environment fails silently. Walk the full flow and confirm each step completes.
Regression after the Agent's next edit
The Agent often edits shared utilities while adding a feature. Lock in known-good journeys and re-run them after each prompt so a fix in one place does not break another.
Build up confidence before you ship
Start in your terminal
Validate on the cloud
Release with confidence
From the editor to a verified deploy
Kane CLI and KaneAI share the same automation engine and dashboard.
Closes the editor-to-deployment gap
The editor preview is not the deployment. Kane CLI verifies the deployed app, where missing Secrets and prod-only 500s actually surface.
Drive it yourself or hand it to your coding agent
Run flows from your terminal against the deployed URL, or pull the project into Cursor or Claude Code and let it drive Kane CLI through the --agent flag, read the result, and fix the break.
Evidence you can share
Every run produces a persistent video, a step trace, and a replay link you can drop into a PR, bug report, or message to whoever asked whether the Replit app really works.
Test your Replit 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 Replit project, you just need the deployed app URL.
Deploy, then point Kane CLI at the live URL
Let the Replit Agent deploy your app, then run flows against the deployed URL yourself or have Cursor, Claude Code, or Codex run them.
Describe the flow and verify
Write the journey in plain English: sign up, create a record, confirm it on the dashboard. Kane CLI drives a real browser, checks 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 deployed app, sign up, create a project, and confirm it shows on the dashboard after a refresh." Kane CLI opens your deployed Replit URL in a real Chrome browser, walks each step, and returns a clean pass or fail with video evidence. Since bugs often surface only on the deployed app, point Kane CLI at the live URL, not the editor preview.
The full-stack apps the Replit Agent generates: CRMs, internal tools, admin dashboards, CRUD apps, task managers, and SaaS MVPs, usually on Next.js or Vite plus React with a PostgreSQL database and Replit's built-in auth. Kane CLI drives the running app in a browser like a user would, regardless of stack, so it works the same whether the Agent shipped a dashboard, an internal tool, or a payment flow.
The Agent writes the frontend, backend, schema, and auth, runs migrations, and deploys to a live URL, often in one prompt. The classic failure is "works in the editor, breaks on deploy": a missing Secret lets a form look saved while the row never lands in Postgres, an API route returns a 500 in production, or a payment key absent from the deployed environment fails silently. The Agent also tends to fix one bug and quietly break another by editing a shared utility or config file. Kane CLI catches these on the deployed app before a user does.
Yes, and this is where it earns its keep. The Agent often touches shared utilities, config, or base components while adding a feature, so a login or form that worked an hour ago can break on the next prompt. Save your known-good journeys, then re-run them after every Agent edit. If a new feature broke an old flow, you see exactly which step failed instead of finding out in production.
Yes. Pull the Replit project into Cursor, Claude Code, or Codex, point the agent at the guide at testmuai.com/kane-cli/agents.md, and it will install Kane CLI, run flows with the --agent flag against your deployed URL, read the structured results, and fix what failed. You build in Replit and verify the deployed app with Kane CLI in the same 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, 3 on timeout. Run your key flows against the deployed Replit URL on every release so a redeploy never silently drops a Secret or breaks an API route.
Teach your agent to test what Replit deploys
Pull your Replit project into your AI coding agent, point it at the Kane CLI guide, and it will install, authenticate, and verify your deployed app in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md