Highlights
WebSocket traffic is now a first-class citizen in kane-cli: you can capture and inspect WS frames alongside regular network activity, and the TUI exposes the toggle right in Config > Run. Several authoring-side fixes tighten up how the AI generates test steps — no more invented field keys, cleaner conditional handling in multi-step flows.
[0.4.8] - 2026-06-25
WebSocket capture, now surfaced end-to-end
- Toggle WebSocket capture from the TUI — a new switch in Config > Run lets you turn WS frame capture on or off without editing config files.
- WS frames appear alongside network activity — WebSocket traffic is folded into the devtools network view, so HTTP and WS events show up in one place during both test runs and authoring sessions.
Smarter AI-generated test steps
- No more invented response field names — when extracting values from API responses, kane-cli now insists on named extractions tied to real fields rather than making up key names.
- Conditionals inside multi-step flows wrap correctly — flows that mix conditional logic with multiple actions no longer produce malformed step sequences.
- Driver and block payloads are treated as literal data — previously, the runner could misinterpret structured payloads; they are now passed through as-is.
Version check that actually works
check-versionreliably detects when a newer release is published — the gate was previously missing live published versions; it now correctly compares against the registry.
Install
# npm
npm install -g @testmuai/kane-cli@0.4.8
# Homebrew
brew install lambdatest/kane/kane-cli
# Shell installer (latest release)
curl -fsSL https://raw.githubusercontent.com/LambdaTest/kane-cli/main/install.sh | bashCompare: 0.4.7...0.4.8