> ## Documentation Index
> Fetch the complete documentation index at: https://www.testmuai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuration
> Configure Kane CLI settings including window size, Chrome profiles, Test Manager project and folder, run mode, and code export.
export const BrandName = ({type = 'default'}) => {
const getBrandName = () => 'TestMu AI';
const getBrandNameLowercase = () => 'testmu ai';
if (type === 'lowercase') {
return getBrandNameLowercase();
}
return getBrandName();
};
***
**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:
```
Read https://www.testmuai.com/support/docs/SKILL.md to set up TestMu AI (formerly LambdaTest) cloud testing.
```
Kane CLI stores persistent settings at `~/.testmuai/kaneai/tui-config.json`. Most settings are managed through `kane-cli config` subcommands; a few are managed through interactive pickers in TUI mode, and one (code export) is toggled from the TUI menu.
Authentication credentials are managed separately under `~/.testmuai/kaneai/profiles/` — see [Authentication](/docs/docs/kane-cli-authentication/).
***
## Viewing Settings
Print the current configuration:
```bash theme={null}
kane-cli config show
```
The output groups settings under three headings:
```text theme={null}
Configuration
Auth
method oauth | basic (user@example.com) | not configured
profile default
env prod
Defaults
url https://kaneai-playground.lambdatest.io
model v16-alpha
mode testing
window 1920x1080
project (none)
folder (none)
Paths
chrome /Users/you/.testmuai/kaneai/chrome-profiles/work
```
Empty fields are shown as `(none)`. The `chrome` path is empty by default, in which case Kane CLI launches Chrome with a temporary profile each run.
***
## Settings Reference
| Field | Type | Default | Description | How to Change |
| ----------------------------- | -------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| `window_size.width` | integer | `1920` | Chrome window width in pixels (800–3840) | `kane-cli config set-window ` |
| `window_size.height` | integer | `1080` | Chrome window height in pixels (600–2160) | `kane-cli config set-window ` |
| `chrome_profile_path` | string | `""` | Path to a Chrome user-data dir. Empty means a fresh profile per run. | `kane-cli config chrome-profile [path]` |
| `default_url` | string \| null | `https://kaneai-playground.lambdatest.io` | Starting URL when a run begins. | `kane-cli config set-url ` |
| `model` | string | `"v16-alpha"` | Reasoning + vision model used by the agent. | Internal default |
| `project_id` | string \| null | `null` | Test Manager project ID for upload | `kane-cli config project [id]` |
| `project_name` | string \| null | `null` | Display name of the selected project | Set by `kane-cli config project` |
| `folder_id` | string \| null | `null` | Test Manager folder ID for upload | `kane-cli config folder [id]` |
| `folder_name` | string \| null | `null` | Display name of the selected folder | Set by `kane-cli config folder` |
| `mode` | `"action"` \| `"testing"` | `"testing"` | Agent behaviour on auth walls, blocked pages, or error pages. | `kane-cli config set-mode ` |
| `target` | `"desktop"` \| `"emulator"` \| `"simulator"` | `"desktop"` | Default run target. `desktop` runs the Chrome browser; `emulator` and `simulator` run against a virtual Android or iOS device (macOS Apple Silicon only). See [Mobile Target](#mobile-target). | `kane-cli config set-target ` |
| `device` | string \| null | `null` | Default mobile device, by name, serial, `ip:port`, or udid. When empty, a TTY run prompts once and saves the choice; a non-interactive run needs `--device` or this key set. Ignored on the `desktop` target. | `kane-cli config set-device ` |
| `app` | string \| null | `null` | Default app under test for mobile runs: a build path (`.apk` or `.zip`) or an uploaded app id. Ignored on the `desktop` target. | `kane-cli config set-app ` |
| `code_export.enabled` | boolean | `false` | Generate code export after upload completes. | TUI menu, or `--code-export` flag |
| `code_export.language` | `"python"` \| `"javascript"` | `"python"` | Output language for generated code. Accepts `python` or `javascript`. | `--code-language ` |
| `code_export.skip_validation` | boolean | `true` | Skip post-codegen worker-side validation. | TUI menu, or `--skip-code-validation` |
***
## Updating Settings
### Window Size
The Chrome window is launched at the configured resolution:
```bash theme={null}
kane-cli config set-window 1280x800
```
The format is `WIDTHxHEIGHT` (lowercase `x` separator). Width must be between 800 and 3840; height must be between 600 and 2160. Invalid values are rejected without changing the saved config.
In TUI mode, the same setting can be edited through an interactive window-size picker.
### Test Manager Project
```bash theme={null}
kane-cli config project
```
In a TTY, this opens an interactive project picker. The picker fetches the projects available to your active profile, lets you search and arrow-key through them, and saves the chosen `project_id` and `project_name`. Login is required before the picker can fetch projects.
You can also set a project ID directly without the picker:
```bash theme={null}
kane-cli config project
```
See [Test Manager Integration](/docs/docs/kane-cli-tms-integration/) for how project selection feeds into uploads.
### Test Manager Folder
```bash theme={null}
kane-cli config folder
```
Opens an interactive folder picker for the currently selected project. Folders are searchable and shown with their hierarchy. You must have a project selected first.
To set a folder ID without the picker:
```bash theme={null}
kane-cli config folder
```
See [Test Manager Integration](/docs/docs/kane-cli-tms-integration/) for how folder selection feeds into uploads.
### Mode
```bash theme={null}
kane-cli config set-mode action
kane-cli config set-mode testing
```
`mode` controls how the agent behaves when a run hits an authentication wall, a blocked page, or an error page:
* **`testing`** (default) — the agent treats those pages as part of the run and continues. Use this when you expect the agent to push through gates that would otherwise stop a real user.
* **`action`** — the agent hard-stops on authentication, blocked, and error pages so you can intervene manually before the run proceeds.
You can override the saved mode for a single run with `--mode ` on `kane-cli run`.
### Mobile Target
On macOS Apple Silicon, Kane CLI can run against a virtual mobile device instead of the desktop browser. Three settings persist the default target and how to reach it. They are a **separate axis** from `mode` above: `mode` tunes agent behaviour, while these choose *what device* a run drives.
```bash theme={null}
kane-cli config set-target emulator # desktop | emulator | simulator
kane-cli config set-device pixel-7 # name, serial, ip:port, or udid
kane-cli config set-app ./builds/app-debug.apk
```
* **`target`**: `desktop`, the default, runs Chrome. `emulator` runs a virtual Android device and `simulator` a virtual iOS device. Existing web runs are unaffected.
* **`device`**: the device a mobile run selects, by name, serial, `ip:port`, or udid. When unset, a TTY run prompts once and saves the choice. Non-interactive runs need it set, either here or with `--device`.
* **`app`**: the app under test for a mobile run, a build path (emulator `.apk`, simulator `.zip`) or an uploaded app id, `APP` followed by six or more digits. Required for every mobile run. On the `desktop` target, `device` and `app` are ignored.
A run reads these as its defaults. Override any of them for a single run with `--target`, `--device`, and `--app`. Setup and the full list of accepted app formats are in [Mobile Testing](/docs/docs/kane-cli-mobile/).
### Code Export
The `code_export` block enables and configures generated code output produced after a successful Test Manager upload. There is no `kane-cli config` subcommand for this block. Set it from one of:
* **The TUI** — open the config menu, choose Code Export, and toggle the `enabled` and `skip_validation` switches.
* **Per-run flags** on `kane-cli run`:
* `--code-export` to enable for this run only
* `--code-language ` to pick the output language (`python` or `javascript`)
* `--skip-code-validation` / `--no-skip-code-validation` to control post-codegen validation
Code export requires a Test Manager upload, so it is only meaningful when a project is configured. See [Test Manager Integration](/docs/docs/kane-cli-tms-integration/) for the full upload pipeline.
***
## Chrome Management
### Chrome Profile
By default, `chrome_profile_path` is empty and Kane CLI launches Chrome with a fresh, temporary user-data directory each run. A clean per-run profile isolates cookies and storage between runs and prevents extensions, password autofill, or signed-in sessions from leaking into automation.
When you select a named Chrome profile, Kane CLI stores it under `~/.testmuai/kaneai/chrome-profiles/` and reuses that directory across runs. This is useful when a test depends on having a logged-in session, a saved address, or a specific extension installed.
### Choosing a Different Profile
```bash theme={null}
kane-cli config chrome-profile
```
In a TTY, this opens an interactive Chrome-profile picker. The picker lists every profile under `~/.testmuai/kaneai/chrome-profiles/` plus a "temporary" entry that clears the path back to empty (per-run fresh profiles). You can also create a new named profile from the picker.
To set a path directly without the picker:
```bash theme={null}
kane-cli config chrome-profile /absolute/path/to/profile
```
### Headless Mode
To run Chrome without a visible window, pass `--headless` on `kane-cli run`:
```bash theme={null}
kane-cli run "Verify the home page loads" --headless
```
Headless mode is per-run; there is no persistent setting. It is the right choice for CI and other environments without a display.
### Window Size
The Chrome window dimensions for both headed and headless modes come from the `window_size` setting. See [Window Size](#window-size) above to update them.
***
## Resetting Settings
There is no `kane-cli config reset` subcommand. To reset persistent settings to defaults, delete the config file:
```bash theme={null}
rm ~/.testmuai/kaneai/tui-config.json
```
Kane CLI recreates the file with defaults the next time it writes a setting. This only resets `tui-config.json`. It does **not** affect:
* Authentication credentials under `~/.testmuai/kaneai/profiles/` (use `kane-cli logout`)
* Session history under `~/.testmuai/kaneai/sessions/`
* Variables under `~/.testmuai/kaneai/variables/` and `.testmuai/variables/`
* Chrome profiles under `~/.testmuai/kaneai/chrome-profiles/`