Test the apps you build with Roo Code before real users sign in
Roo Code ships features fast inside VS Code, but it never sees the rendered UI, so signup, forms, and the deployed build can break for real users. Point Kane CLI at your running app and verify the flow in a real browser. Free to install.
or read the documentation
Why test apps built with Roo Code
Roo Code is an open-source AI coding agent that runs in VS Code and autonomously writes and edits frontend and backend code across your project. That speed is the point, but it reasons over source, never the running app.
That is the blind spot. A button wired to the wrong handler, a signup that silently fails, a redirect that 404s, or a form that never persists all read as correct in the diff and only break once a real user clicks through in a browser.
Kane CLI is the second pair of eyes. Describe the journey in plain English and it drives your live app in a real Chrome browser, signs up fresh, and verifies each step. Roo Code can even run Kane itself via the --agent flag.
What Kane CLI tests in your Roo Code app
Signup, forms, data isolation, and the deployed build, verified for a real user.
Signup and auth for a fresh user
Sign up as a new account, confirm the redirect after login, and verify the session holds. Roo Code can wire auth that works for you and breaks for the next user, so test it as a real signup, not your own logged-in tab.
Forms and CRUD that persist
Submit the forms Roo Code generated, check validation, and confirm the row lands and reads back. Catch the silent insert that looks wired in the code but never reaches the database.
Multi-user data isolation
Create records as one user, log in as another, and confirm neither can see or write the other's data. Catch the missing access check before one account reads everyone's rows.
Checkout and payment flows
Walk the full purchase flow, upgrade and downgrade a plan, and confirm the tier actually changed, so a broken checkout never reaches a paying customer.
The build Roo Code deployed, not just the diff
Run against the live domain Roo Code shipped to and catch the blank screen from a missing env var, a refresh that 404s on SPA routing, and asset chunks that vanish after a redeploy.
Regression after every Roo Code edit
Roo Code edits code across your whole project, and its next task can quietly break a flow it touched two files away. Lock in the journeys that already passed and re-run them after each Roo Code change.
Build up confidence before real users sign in
Start in your terminal
Validate on the cloud
Release with confidence
Built for the build-then-verify loop
Kane CLI and KaneAI share the same automation engine and dashboard.
One loop: Roo Code builds, Kane verifies
Roo Code turns your prompt into working frontend and backend inside VS Code, then Kane CLI opens the result and confirms the generated auth, data, and checkout actually work for a real user before the task is done.
Catch what the source code hides
Roo Code edits files and trusts the diff, never the rendered page. Kane CLI loads that page in a real Chrome browser and clicks through it, surfacing the silent failures Roo Code cannot see from the code alone.
Proof to hand back to Roo Code or your team
Every run leaves a persistent video, a step trace, and a replay link, so Roo Code can act on a clear pass or fail and you can drop the same evidence into a PR or bug report.
Test your Roo Code app in three steps
Install Kane CLI
Run npm install -g @testmuai/kane-cli and sign in with your TestMu AI account. It sits alongside Roo Code, with nothing to wire into your VS Code workspace or project config.
Point it at the app Roo Code built
Aim it at your local dev server while Roo Code is still iterating, or at the deployed domain once it ships. Run flows yourself from the terminal, or let Roo Code launch them after a task.
Describe the journey Roo Code built and check it
Write the flow in plain English, such as sign up, submit a form, and confirm the record persists. Kane CLI walks the running app as a real user, confirms each step held, and hands back a clear pass or fail with video and a shareable link.
Get Started With Kane CLI
🎉 Launch offer: Bonus credits for the first 3 months on paid plans
Choose the right plan for you
Local test authoring via CLI
Auto-heal & vision
View test cases on UI
Test Manager
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Choose the right plan for you
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Get the technical rundown
Documentation
Everything you need to install, configure, and run Kane CLI in under 2 minutes.
Frequently asked questions
After Roo Code finishes a task in VS Code, install Kane CLI and describe the journey you asked Roo Code to build, for example "open the running app, sign up as a new user, submit the form, and confirm the record shows on the dashboard." Kane CLI opens the live app Roo Code generated, walks each step as a real user, and tells you whether the feature actually works with video to back it up. Run it against your local dev server or your deployed domain straight from the terminal.
Roo Code is an autonomous coding agent inside VS Code, and it writes and edits frontend and backend code across your whole project from a prompt. It is fast, but it reasons over source code and never renders the running app. So a button wired to the wrong handler, a redirect that 404s, a signup that silently fails, or a form that never persists all read as correct in the diff and only break in the browser. Kane CLI verifies the real flow, as a real user, before you ship.
The full signup and login journey for a new user, create-read-update-delete on the forms and tables Roo Code generated, multi-user data isolation, checkout and payment flows, and the deployed build rendering instead of a blank screen. It also catches SPA 404s on refresh, console errors, and broken API calls. It checks each step, not just the final screen, and flags the exact point where the app breaks.
Yes. Roo Code executes shell commands as part of its task loop, so point it at the guide at testmuai.com/kane-cli/agents.md and it installs Kane CLI and runs flows with the --agent flag, which streams NDJSON it can parse step by step. Roo Code reads the structured result, then reopens the file it just changed and fixes the broken handler or form before you ever load the page.
Yes. Once Roo Code commits and you push, Kane CLI runs in the pipeline the same way: authenticate with your TestMu AI credentials, pass --headless and --timeout, and gate the build on the exit code, with 0 on pass, 1 on fail, 2 on setup or auth errors, and 3 on timeout. Replay your signup, CRUD, and checkout flows on every deploy so a redirect Roo Code rewired or a missing env var never reaches production.
Kane CLI is free to install and run locally, which covers verifying everything Roo Code builds on your own machine, no credit card needed. When you want the same flows replayed across the TestMu AI cloud grid on every deploy, those cloud runs are billed against your TestMu AI plan. Start on the free tier and prove your Roo Code app end to end first.
Teach Roo Code to test what it builds
Roo Code can run shell commands. Point it at the Kane CLI guide and it will install, authenticate, and verify the signup, form, and checkout flows in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md