Skip to main content
Using Claude Code, Cursor, or another coding agent? Paste this into your prompt to run cross-browser and real-device tests, debug sessions, and wire up CI on the TestMu AI cloud:
Kane CLI is published to the public npm registry as @testmuai/kane-cli and to a Homebrew tap. Install it with npm or brew to get the kane-cli command on your PATH.

​
Install

Requires Node.js 18 or higher.
Platform-specific native binaries are installed automatically for your OS. No additional configuration is needed.
Kane CLI requires Google Chrome installed on your system. Chrome is used as the automation browser and is launched automatically when you run a test. The npm install additionally requires Node.js 18 or higher. The Homebrew install bundles Chrome for you and needs no Node.js.

​
Install with pnpm or yarn

Installing kane-cli via pnpm is not currently supported. pnpm places packages inside a nested node_modules/.pnpm/ store, so the project-root node_modules/ ends up deeper on disk than it would with npm. kane-cli’s resolver for the platform-specific v16-runner binary does not yet search that far up the directory tree, so the runner is never found and the CLI aborts. The symptom is a silent exit with status 2 shortly after startup — see CLI exits with code 2 and no output in the troubleshooting guide. This limitation is tracked in issue #24. Until that is resolved, install kane-cli through one of the supported paths:
  • npm globally (npm install -g @testmuai/kane-cli, above).
  • Homebrew on macOS or Linux (brew install LambdaTest/kane/kane-cli). Does not require Node.
  • The shell installer for any POSIX system (curl -fsSL https://raw.githubusercontent.com/LambdaTest/kane-cli/main/install.sh | sh).
yarn (classic and Berry) has not been verified end-to-end. If you use yarn, prefer the Homebrew or shell-installer path until it is explicitly supported.

​
Verify

Expected output:
If the command is not found, your shell is not seeing the npm global bin directory. Open a new terminal or update PATH, then try again.

​
Platform Support

Mobile testing, the iOS Simulator and the Android Emulator, is supported on macOS Apple Silicon (arm64) only for the initial release. See Mobile Testing for the simulator and emulator prerequisites.

​
Update

Kane CLI checks the npm registry once every 24 hours when you launch it. When a newer version is available, the CLI prints a one-line notification on startup with the current and latest versions. The check runs in the background and never blocks startup. Upgrade with:
After upgrading, run kane-cli --version to confirm the new version is active.

​
Uninstall

This removes the kane-cli binary but leaves your local data in place. Kane CLI stores credentials, configuration, sessions, and Chrome profile data under ~/.testmuai/kaneai/. To wipe that state as well:
Only do this if you want a clean reset — it logs you out of all profiles and deletes saved configuration, session history, and command history.

​
Troubleshooting Installation

kane-cli: command not found after install Your npm global bin directory is not in your PATH. Find it and add it:
Installation fails on Node 16 Kane CLI requires Node.js 18+. Check your version and upgrade if needed:

​
Next Step

Quick Start: Authenticate and run your first test.