Test the features Cursor edits across your app before you merge
Cursor's agent rewrites whole features across many files, and code that compiles can still hide a broken flow. Kane CLI re-runs your user journeys in a real browser and returns a clean pass or fail. Free to install.
or read the documentation
Why test apps built with Cursor
Cursor is an AI code editor whose agent edits whole features across dozens of files at once, and runs agents in parallel on separate Git branches. It rewrites your existing codebase, so its output must coexist with what you ship.
That is why the running app needs verifying. One edit ripples through the codebase, so an ambitious refactor can quietly break a flow that worked a minute ago while the code still compiles. The bugs live in the journeys.
Kane CLI is that check. Describe the journey in plain English and it drives your running app in a real Chrome browser, clicks the flow, and tells you where it breaks. Agent-native, so Cursor's agent can run it itself.
What Kane CLI tests in your Cursor app
From the flow a new feature added to the regressions a wide refactor hides, verified in a real browser.
Regression after every agent edit
Cursor's agent rewrites code across many files at once. Lock in your known-good journeys and re-run them on each edit so a ripple in one file never breaks a flow three screens away.
The flow the new feature added
After the agent ships a feature, walk its end-to-end path: the new route, form, and state it added. Confirm the whole journey works, not just that it compiles.
Auth, sessions, and protected routes
Cursor apps lean on Supabase or NextAuth. Verify sign-up, login, logout, and that protected pages and role checks still hold after a refactor touches the auth layer.
Data writes that actually persist
Walk the create, edit, and delete paths and confirm the record lands and survives a reload. Catch the silent API or database failures a fast edit can introduce.
No console errors or broken routing
Crawl the running app for broken links, missing assets, dead routes, and console errors that only surface in a real browser, the kind a compile pass never sees.
Parallel branches, verified
When several Cursor agents push to separate branches, run the same flows against each preview URL to know which branch is safe to merge.
Build up confidence before you merge
Start in your terminal
Validate on the cloud
Release with confidence
Built for the edit-then-verify loop
Kane CLI and KaneAI share the same automation engine and dashboard.
From a multi-file edit to a verified journey
Cursor edits the feature across files; Kane CLI proves the running app still works. Close the gap between a wide multi-file change and a verified user journey before you merge.
Cursor drives Kane CLI from its own terminal
Cursor's agent already runs shell commands. Point it at the guide, let it call Kane CLI with the --agent flag, read the structured result, and fix the break it caused, all in one agent run.
A safety net for the ambitious refactor
The fast, far-reaching edits Cursor is good at are exactly the ones that break things quietly. Re-run your saved flows on every change and catch the regression the moment it lands.
Test your Cursor 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 Cursor workspace or build.
Point Cursor at the guide, or run it yourself
Add testmuai.com/kane-cli/agents.md so the Cursor agent runs flows with the --agent flag after it edits, or run them yourself from the terminal against your local or preview URL.
Describe the flow and verify
Write the journey in plain English. Kane CLI drives a real browser, checks each step, and returns a pass or fail with video you can drop into the PR.
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
Run your app locally or on a preview URL, install Kane CLI, and describe the journey in plain English, for example "log in, open the dashboard, create a record, and confirm it shows in the list." Kane CLI drives the running app in a real Chrome browser, checks each step, and returns a clean pass or fail with video. Run it from your own terminal, or let the Cursor agent run it as the last step of the feature it just wrote.
Yes. Kane CLI is built for AI coding agents, and Cursor's agent already runs terminal commands. Point it 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 break before it hits your PR. Cursor edits the feature across files, then verifies the running app in a real browser, in the same agent run.
Cursor's agent edits whole features across many files at once, and one change ripples through the codebase. That speed is where regressions hide: an "ambitious refactor" can quietly break a login flow, a route, or a form that worked a minute ago, and the code still compiles. With parallel agents on separate branches, more lands per day than anyone can click through by hand. Kane CLI re-runs your known-good journeys in a real browser so a ripple from one edit does not ship as a broken flow.
That is the main job. Save the journeys that matter, login, your core create-edit-delete path, checkout, and re-run them after every Cursor edit or merge. When the agent touches twenty files to add a feature, Kane CLI tells you within minutes whether the existing flows still pass, so a wide refactor does not silently break something three screens away.
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. Run your key flows on every PR and deploy, including the branches your parallel Cursor agents push.
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 app you build in Cursor end to end without a credit card.
Teach your agent to test what it builds
Point the Cursor agent at the Kane CLI guide and it will install, authenticate, and verify your running app in a real browser from its own terminal.
Point your agent to: testmuai.com/kane-cli/agents.md