Can I run Kane Exploration from the CLI and the cloud?

Yes, you can start a Kane CLI exploration with kane-cli explore run in your terminal, or a KaneAI exploration in the cloud from your KaneAI account.

What does a Kane CLI exploration need to start?

A Kane CLI exploration needs only the URL of your web app, passed to kane-cli explore run --url, plus an optional --policy flag.

Where does an exploration run, and how many browsers does it use?

Every exploration runs on HyperExecute by default with one cloud browser, and the --max-parallel flag raises that to as many as 20 cloud browsers.

Can I watch an exploration while it runs?

Yes, kane-cli explore view opens the live exploration map in your browser and shows the run's screens, flows, findings and credits as they grow.

Will exploration change data in my app?

Kane Exploration changes data under the default mutating policy, which also presses controls such as Delete, Sign out and Pay. The read_only policy blocks POST, PUT, PATCH and DELETE requests and never presses those controls.

What kinds of findings does KaneAI exploration flag?

KaneAI exploration flags anything that looks broken and any place the explorer could not get past, and each finding carries screenshots, the steps that led to it, and network and console logs.

How are passwords and other secrets handled?

Values marked as secret go to HyperExecute Secrets instead of the request itself, and Kane CLI masks secrets before they reach disk, logs or an Evidence Pack.

Can Kane Exploration test localhost or private apps?

Yes, a tunnel running on your machine lets a Kane CLI exploration reach localhost and other private apps.

How long can one exploration run?

One exploration run stops after one hour, 400 actions or 800 model calls, whichever comes first, and the run then ends with the status budget.

Does a re-explore start from scratch?

No, each project holds one exploration of one URL, and every re-explore adds to that exploration map. The --focus flag can start the new run from one screen of the map.

How does Kane Exploration turn the map into tests?

Design jobs turn the exploration map into use cases, scenarios and tests in Test Manager, and a person reviews them. Exploration never runs those tests itself, and the first run of each pulled test records its steps in a real browser.

Does Kane Exploration work on mobile apps?

Kane Exploration works on web apps today, while the rest of Kane CLI tests web apps in real browsers and mobile apps on iOS simulators and Android emulators.

Which plan includes KaneAI exploration?

KaneAI exploration comes with the KaneAI Max plan, which includes three exploration sessions per licence.

Kane Exploration maps and tests your web app

Q: What is Kane Exploration?

Kane Exploration maps every screen, control and flow of a web app from one URL, flags findings, and designs tests from that exploration map.

Start Kane Exploration from Kane CLI or KaneAI in the cloud, and up to 20 cloud browsers map every screen, control and flow of your web app.

npm install -g @testmuai/kane-cli

Trusted by 3M+ users globally at

+Read case study

What is Kane Exploration?

Kane Exploration walks your web app on cloud browsers and maps every screen, control and flow, started from Kane CLI in your terminal or from KaneAI in the cloud.

Kane Exploration turns a URL into a map and tests

One command explores the app in the cloud, keeps a live map, ships evidence for each finding and writes tests from the map.

Start free with Google

Explore your web app in up to 20 cloud browsers

The explore run command sends every exploration to HyperExecute by default, and HyperExecute opens a cloud Chrome browser only when the exploration agent asks for one.

Learn more

Scope with -‌-focus: The -‌-focus flag starts an exploration from one screen of an existing map.
Cap with -‌-max-parallel: The -‌-max-parallel flag raises a run from one cloud browser to 20.
Stop with explore stop: The explore stop command ends a queued or running exploration cleanly.

Kane CLI exploration run on HyperExecute with 20 cloud browsers, 15 screens mapped and 64 findings

The exploration map shows every screen, control and flow

The explore view command draws the exploration map live, with each screen's controls, the flows in and out, and every state the screen has shown.

Learn more

Live view: Live view streams any cloud browser at up to 15 frames a second while the exploration runs.
Built for big apps: Search, zoom and a legend keep exploration maps of thousands of screens easy to read.
One map per project: Every re-explore adds to the project's existing exploration map instead of starting over.

Kane CLI exploration map with screens, controls and flows

Every finding comes with screenshots, logs and a clip

Every exploration finding carries an Evidence Pack with a clip, Network and Console tabs, before and after screenshots, the cause chain and a verdict.

Learn more

Re-checked: Re-check leases run each finding again to confirm it reproduces.
Tracked to resolved: A finding's status moves from open to bug, resolving, resolved or discarded.
Full history: The finding history names who changed each status, and when.

Kane CLI exploration finding with its Evidence Pack

Kane CLI writes tests from the exploration map

Kane CLI reads the exploration map as context to design use cases and acceptance criteria, and a person approves the tests before they go into CI.

Learn more

Unattended design: The explore assurance-job command runs the test design chain unattended.
Reviewed by a person: A person approves each test, because the map can include today's bugs.
Runs in CI: Approved tests run in CI on every pull request, with an Evidence Pack.

Use cases and acceptance criteria Kane CLI designed from the exploration map

Run your first Kane CLI exploration

Install Kane CLI, point the explore command at your web app and open the exploration map.

Every explore command and flag is in the Kane CLI exploration docs. Check out our documentation

Copied to Clipboard!

Six Kane Exploration checks on every screen

You do not choose what to look for before an exploration starts, because all six detectors run on every screen the exploration map reaches.

Console errors

The console detector records the errors a page logs during a run.

Network failures

The network detector flags failed requests and off-domain POSTs.

Broken links

The broken link detector flags links that lead to no working page.

Slow requests

The slow-request detector flags requests over the slow budget.

Accessibility checks

The accessibility detector reports each failed axe-core rule.

Re-checks

A re-check runs each finding again to confirm it reproduces.

How a Kane CLI exploration goes from a URL to CI

A Kane CLI exploration takes four steps from the terminal, and the map and its findings stay in one project.

1. Point it at a URL

The explore run command takes a URL and a run policy.

2. Explore in the cloud

HyperExecute explores with up to 20 cloud browsers.

3. Review the map

The explore view command shows the map and findings.

4. Ship the tests

Approved tests from the map run in CI on every pull request.

Choose how Kane Exploration touches your app's data

Each exploration runs under one of two policies, and Kane CLI masks secrets under both.

Read-only policy

The read-only policy blocks POST, PUT, PATCH and DELETE requests.

Mutating policy

The default mutating policy submits forms and presses every control.

Secret masking

Passwords and tokens never reach disk, logs or an Evidence Pack.

Some Love from our Customers

As Best Egg expanded its product offerings and entered new markets, we knew our old testing infrastructure couldn’t keep up.
With support from Tenny Agustin, our Engineering Operations Lead, we modernized our approach with

TestMu AI

Best Egg

best-egg

Excited to Share My Learning Journey with Kane AI & Lambda Tool!
I'm pleased to announce that I've recently gained hands-on experience exploring Kane AI through the Lambda Tool and it’s been a fantastic journey of upskilling!

KaneAI

Suryateja Goud

suryateja-goud

See how is #Futureready to enable blazing-fast test orchestration seamlessly integrated with organizations' existing CI/CD platforms, using #Microsoft Azure.

TestMu AI

Microsoft India

MicrosoftIndia

View all reviews

More Reasons to Love TestMu AI

TestMu AI is a leading agentic AI quality engineering platform, trusted globally, that assures your AI deployments work as intended, safely and securely, across enterprise and real-world conditions.

Start free with Google

Users

3M+

Tests

1.5B+

Enterprises

18K+

Countries

132