Test the apps you build with Cline not just the test suite
Cline's tests go green, but can a user click through the running app? Kane CLI drives the live app in a real browser, verifies each flow in plain English, and Cline can run it in its own loop. Free to install.
or read the documentation
Why test apps built with Cline
Cline is an open-source autonomous coding agent in VS Code, JetBrains, and the terminal. Plan mode proposes an approach, then Act edits files and runs commands, scaffolding a feature and iterating until your tests pass.
That implement-test-fix loop makes Cline fast, and is why the running app needs a second look. Green tests confirm units, not that a real user reaches the end, and one browser_action screenshot is not a verified flow.
Kane CLI is that second pair of eyes: describe the journey in plain English and it drives your live app in real Chrome and reports where it breaks. Cline already runs terminal commands, so it can run Kane CLI via the --agent flag itself.
What Kane CLI tests in your Cline app
The running flow Cline built, verified in a real browser, beyond the green test run.
The flow Cline just built
Run the actual user journey for the feature Cline scaffolded, from entry point to final confirmed action, and prove the whole path works, not just that the test suite went green.
Forms and validation it wired up
Submit the forms Cline generated, check validation messages, and confirm the data reaches the right route and reads back. Catch the silent post to the wrong endpoint a passing unit test never noticed.
Auth and protected routes it touched
When a task changes login, sessions, or guarded pages, sign up, log in, and confirm protected routes behave for both a fresh and a returning user, instead of redirecting to a blank screen.
New API and backend routes
Cline adds endpoints, handlers, and database calls in the same task. Drive the flow that hits them and confirm the real response renders in the UI, not a 500 or an empty state the screenshot hid.
No console errors or broken navigation
Walk the running app in a real Chrome browser and surface the console errors, broken links, and dead buttons a Puppeteer screenshot of a single frame steps past.
Regression on the next Act-mode edit
Cline edits real code across your project, so the next approved task can break a flow that worked a minute ago. Lock in known-good journeys and re-run them on every change to catch the regression instantly.
Build up confidence before you ship
Start in your terminal
Validate on the cloud
Release with confidence
Built for the implement-test-fix loop
Kane CLI and KaneAI share the same automation engine and dashboard.
Built for the implement-test-fix loop
Cline already runs your test suite, reads stderr, and iterates until it passes. Kane CLI adds the missing step: it drives the running app in a real browser so the loop closes on a verified user journey, not a green test run.
Cline drives the browser run itself
Cline runs terminal commands in its loop, so it can call Kane CLI through the --agent flag, read the structured pass or fail, and fix the break in the same Act-mode pass, just as it parses test output.
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 team message, instead of a single screenshot Cline captured mid-task.
Test your Cline 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 project; it runs alongside Cline in the same terminal.
Let Cline run it, or run it yourself
Point Cline at the Kane CLI guide so it runs flows with the --agent flag in its loop, or run flows from your terminal against your live app URL after Cline finishes a task.
Describe the flow and verify
Write the journey in plain English, like sign up, create a record, and confirm it shows on the dashboard. 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 app, sign up, create a project, and confirm it appears on the dashboard." Kane CLI drives your running app in a real Chrome browser, checks each step, and returns a clean pass or fail with video evidence. Since Cline runs in your terminal and editor, you can run Kane CLI yourself or have Cline run it in its implement-test-fix loop by pointing it at the guide at testmuai.com/kane-cli/agents.md.
Cline runs in Plan then Act mode: it scaffolds a feature across files, runs your test suite, reads stderr, and iterates until tests go green. But a green Vitest or Jest run does not answer the real question, whether a user clicking through the running app reaches the end of the flow. Tests can pass while login redirects to a blank page, a form posts to the wrong route, an empty state never renders, or a console error breaks the page. Cline can also confirm a change with a single browser_action screenshot, but one frame is not a verified end-to-end journey. Kane CLI drives the live app like a real user, so you catch the break the unit tests missed.
The end-to-end flow of the feature Cline just built, the forms and validation it wired up, the auth and protected routes it touched, the new API or backend routes it added, and the absence of console errors or broken navigation in a real browser. Since Cline edits real code across your project, Kane CLI also re-runs known-good journeys to catch a regression the next Act-mode task introduced. It checks each step, not just the final screen, and flags the exact point where the app breaks.
Yes, and it fits naturally because Cline already runs terminal commands and reads their output during its loop. Point Cline at the guide at testmuai.com/kane-cli/agents.md and it will install Kane CLI, run flows with the --agent flag, parse the structured pass or fail, and fix the broken flow in the same Act-mode pass, just as it already reads stderr from your test suite. Build with Cline, verify the running app 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 the key flows of the app Cline built on every push, so a regression from the last Act-mode edit never reaches production even when unit tests are green.
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. Cline itself is open source, so you can verify your Cline app end to end without a credit card.
Teach your agent to test what it builds
Cline already runs your test suite and reads the output. Point it at the Kane CLI guide and it will install, authenticate, and verify the running app it built in a real browser inside the same loop.
Point your agent to: testmuai.com/kane-cli/agents.md