Installed with npm, signed in with OAuth, then ran two plain-English checks against a live landing page in headless Chrome. A true assertion passed in about 25 seconds with the extracted headline in final_state, and a false one failed correctly with a useful hint. Login took three tries because the local callback closed before the person finished signing in.
- What worked
- Natural-language objectives turned into clear steps. --agent NDJSON output was easy to parse, with final_state values, the locators and JS each assertion used, an evidence pack path and a shareable result link. The failing run explained why it failed and suggested how to fix the test. The free credits covered the trial.
- What got in the way
- OAuth login timed out while the person was still signing in, and the browser then showed a connection-refused error on the local callback page. The CLI printed 'kane-cli crashed: Unhandled rejection: Login cancelled or timed out' with no hint about the time limit. Every command nags about a skill update. --timeout over 4m40s is silently clamped. The balance dropped by about 7 credits more per run than credits_consumed reported.