Custom Models (Browser Use) alternative with no model to manage
Kane CLI is the Custom Models alternative with no model to choose, wire, or pay per token for. Natural-language browser automation on a managed model that drives a real browser, self-heals, and verifies pass or fail. Free to install.
or read the documentation
Why teams pick a managed model over Custom Models
Custom Models are LLMs purpose-built for browser automation, which is a real advantage if you want to pick and tune the model yourself. The cost is that you do pick, wire, and pay per token for the model on every run.
Kane CLI takes the opposite stance: a managed reasoning model ships with the tool, so there is nothing to choose, configure, or meter. You give it a natural-language objective and it drives a real browser and returns a pass or fail.
Validated flows replay from a cached test.md with no repeat LLM cost, so the managed model stays cheap to run in CI, and any flow exports to native Playwright with one command.

Kane CLI vs Custom Models
Custom Models hand you the model. Kane CLI manages it, so there is nothing to choose or meter.
| Capability | Kane CLI (TestMu AI) | Custom Models |
|---|---|---|
| Model choice | Managed model, nothing to choose | Pick a browser-tuned model |
| Wiring | Install and go, no keys | Wire the model and keys |
| Cost model | Credits plus cached replay, no per-token surprise | Pay per token per run |
| Authoring | Natural-language objectives, no code | Model powers your own automation |
| Verified pass or fail | Built-in assertions, pass or fail with evidence | Depends on your harness |
| Native Playwright export | One command |
What you get with Kane CLI
The convenience of a managed model, with a production verdict on top.
No code, no keys
Skip the SDK wiring and the model and API key setup. Install one CLI, describe the journey in natural language, and Kane CLI drives a real browser with a managed model.
Resilient by default
When the frontend changes, Kane CLI adapts on its own, pushing through up to 50 steps until the full journey is verified instead of breaking on a moved element.
Verified pass or fail
Built-in assertions check each step, not just the final screen, and flag the exact point of failure. A real result, not raw agent output to parse.
Replay and caching
Validated flows replay from a cached test.md with no repeat LLM cost, so re-running the suite in CI does not keep burning tokens.
Cross-browser cloud and CI
Scale to cross-browser and cross-OS runs on the TestMu AI grid with one flag, and gate pipelines on clean exit codes from your terminal.
Own the Playwright code
Export any validated flow to native Playwright with one command, then modify and own it. The convenience never locks you in.
Build up confidence locally

Start in your terminal

Validate on the cloud

Release with confidence
From prototype to production, on one engine
Kane CLI and KaneAI share the same automation engine and dashboard.
Prototype to production
Open-source agents and SDKs are great for prototyping. Kane CLI is the production-grade, test-focused path: assertions, caching, evidence, and CI built in.
Built for the agent loop
Generate code, then verify it in a real browser before opening a PR. Kane CLI closes the gap between what an agent writes and what works.
Evidence you can share
Every run produces a persistent video, step trace, and replay link to drop into a PR or bug report, backed by a dashboard your team can browse.
Skip model management in three steps
Install
Run npm install -g @testmuai/kane-cli, then sign in with your TestMu AI account. No project to scaffold and no API keys to manage.
Describe the flow
Tell Kane CLI what to do in natural language, or point your AI coding agent at the agent guide and let it drive the browser.
Run and verify
Kane CLI drives a real browser, verifies each step, and returns a pass or fail with video proof. Re-runs replay from cache with no repeat LLM cost.
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
Kane CLI by TestMu AI is a strong Custom Models alternative when you would rather not manage a model at all. Custom Models are LLMs you pick, wire, and pay per token for. Kane CLI ships a managed reasoning model, so you give it a natural-language objective and it drives a real browser and returns a verified pass or fail, with no model to choose or meter.
Custom Models, from Browser Use, are LLMs purpose-built for browser automation. They can improve automation quality, but you select, integrate, and pay per token for the model yourself.
Kane CLI does not ask you to choose or manage a model. It ships a managed model, self-heals with confidence-scored matching, returns a pass or fail with evidence, replays from a cached test.md with no repeat LLM cost, and exports to native Playwright with one command.
Teach your agent the right skills
Point your AI coding agent at the Kane CLI guide and it will install, authenticate, and run verified browser flows on its own, no SDK or API keys required.