Codeless browser testing in plain English
Describe the test the way you would explain it to a teammate. No selectors, no framework, no scripting. Kane CLI drives a real browser and returns a verified pass or fail with evidence. Free to install.
or read the documentation
No-code browser testing, for everyone
Codeless testing means you write the objective in plain English, not a script. There are no selectors to find, no XPath to maintain, and no framework to learn. You describe the outcome and Kane CLI resolves the path.
That makes browser testing accessible to people who never touch a test framework. PMs, designers, QA, and vibe coders can author a flow alongside developers. If you can describe a journey, you can verify it in a real browser.
No-code does not mean locked out of code. Autoheal removes the maintenance that sinks most codeless tools, and any run exports to Playwright the moment a developer wants real source to read and commit.
What makes Kane CLI codeless
Plain-English objectives, no selectors, verified results, and an export path to code.
Plain-English objectives, no selectors
State the journey the way you would walk a teammate through it. No CSS selectors, no XPath, no Page Object Model. Kane CLI reads the objective and finds its own way through a real browser.
Built for people who do not code
Product managers, designers, QA, and vibe coders can build a test without ever opening a framework. Describe the flow and you can verify it. No Python, no Selenium, no starter project to wade through first.
A verified verdict, not a click recording
Codeless here is not a fragile recorded macro. Each run anchors to what a real user actually sees and hands back a clear pass or fail, backed by a video, a step trace, and a replay link you can share.
Autoheal keeps no-code tests alive
Reword a label or swap a class and autoheal locks back onto the target instead of breaking. With no selector file to patch, the upkeep that quietly kills most codeless tools simply is not there.
Export to Playwright when you want it
Need real source? Export any run to native Playwright. No code to author and confirm a flow, full code the moment a developer wants to read, edit, or commit it. The code path is always open.
Lives in your terminal, not a SaaS tab
Drop the recorder UI and the browser tab stuffed with steps. Kane CLI runs from your terminal, locally or in CI, and slots into the workflow you already have, with no cloud project to set up first.
Verify any flow without writing a line of code
Start in your terminal
Validate on the cloud
Release with confidence
Describe the outcome, not the script
Kane CLI and KaneAI share the same automation engine and dashboard.
Write the requirement, skip the script
Most codeless tools still leave you recording clicks and repatching selectors every time the UI moves. Kane CLI takes a plain-English objective and works out the steps itself, so a test ends up reading like the requirement it is checking.
Open to everyone, code optional
A PM or designer can author and run a flow without writing anything, and a developer can export that same run to Playwright whenever they like. Codeless drops the barrier for newcomers without capping what an engineer can do next.
Proof anyone on the team can open
Each run leaves behind a stored video, a step trace, and a replay link you can paste into a PR, a bug ticket, or a chat thread, so even a no-code test ships with evidence the whole team can review.
Run a codeless test in three steps
Install Kane CLI
Run npm install -g @testmuai/kane-cli and log in with your TestMu AI account. Nothing to scaffold, no selector library to assemble, nothing to bolt onto your app first.
Say the flow in plain English
Type the journey out loud the way you would describe it: open the app, sign up, create a record, confirm it appears. No selectors, no scripting, no boilerplate at all.
Run it and read the verdict
Kane CLI walks each step in a real Chrome browser and hands back a pass or fail with video to back it up. Run it again whenever you like, or export to Playwright once a developer wants the code.
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
Codeless testing lets you state what a test should accomplish in plain English instead of coding it. You type an objective such as "open the app, sign up as a new user, and confirm the dashboard loads," and Kane CLI works out the steps in a real browser for you. There is nothing to select, no XPath to author, and no framework scaffolding to learn. The result is genuine browser testing that a non-developer can run without ever opening a script file.
Anyone who can put a user journey into words. Product managers who know the flow but do not write Python, designers checking their own components, QA folks who would rather skip selector upkeep, and vibe coders shipping through AI. Developers reach for it too, since stating an objective beats hand-writing a spec. With a natural-language interface, the only skill that matters is deciding what to verify, not learning how to script it.
Running a test never requires you to write a single line. Codeless still leaves the door to code wide open, though: any run exports to native Playwright whenever a developer wants source they can read, edit, or commit. A PM or designer can build and confirm a flow with no code at all, and a developer can pick up that exact run later and turn it into a Playwright test. You start no-code and add code only if you choose to.
Old-school codeless recorders snap the instant a button gets a new class or a label is reworded, and someone has to record the whole thing again. Kane CLI ties each step to the element a real user sees rather than a fragile selector, so autoheal locks back onto the target when the page shifts. Everyday cosmetic drift is handled for you. When a change is big enough that the correct element is truly unclear, Kane CLI flags it rather than papering over a real bug. No selector file ever needs tending.
Yes. The very plain-English objectives you run on your laptop also run headless in a pipeline. Sign in with your TestMu AI credentials, add --headless and --timeout, and let the build react to the exit code: 0 for pass, 1 for fail, 2 for setup or auth trouble, and 3 for timeout. Because there is no script to write, a non-developer can author the flow and it will still fire on every commit across GitHub Actions, GitLab, Jenkins, or Bitbucket.
Installing and using the CLI costs nothing. Runs on your own machine are free, while cloud runs on the TestMu AI grid draw against your TestMu AI plan. Begin on the free tier and confirm a real browser flow in plain English, no code and no credit card needed to get going.
Hand codeless testing to your coding agent
Point your AI coding agent at the Kane CLI guide and it will install, authenticate, and verify your flows in a real browser from plain-English objectives, no scripting required on either side.
Point your agent to: testmuai.com/kane-cli/agents.md