TestMu AI
World's first full-stack Agentic AI QE Platform.
4.8•12 reviews•2.6K followers
World's first full-stack Agentic AI QE Platform.
4.8•12 reviews•2.6K followers
TestMu AI is a Full Stack Agentic AI Quality Engineering platform that helps teams test intelligently and ship faster. Built for scale, it delivers end-to-end AI agents that plan, author, execute, and analyze software quality across web, mobile, and enterprise apps on real devices, browsers, and environments. Going beyond automation, TestMu AI Agents bring agentic intelligence to the entire SDLC, continuously boosting the speed, accuracy, and depth of testing.
This is the 14th launch from TestMu AI. View more
Kane CLI
Launching today
An agentic quality verifier for developers and AI coding agents. Describe a test in natural language, and Kane CLI runs it in a real Chrome browser and returns pass or fail with shareable proof. No selectors to write. Local-first, free to start.
Free Options
Launch Team / Built With
TestMu AI
Hi, I'm Jay Singh, Co-Founder of TestMu AI.
Every technology wave has the same shape. Capability jumps first. Trust catches up later. We saw it with cloud, and we are watching it again with AI.
The gap we kept seeing
⚡ AI writes the code in minutes now
🖱️ But someone still has to open the app and confirm it actually works
⏳ The building got fast. The assurance never did
That gap is the defining problem of this era of software, and it is why we built Kane CLI.
How it closes the loop
📥 Ingests your source or PRD
🧩 Designs the use cases and test scenarios
🌐 Runs them in a real Chrome browser, or on Android emulators and iOS simulators
📸 Returns an evidence pack, AC coverage, and a verdict
Not just "did it run". Did it work, and can you prove it. ✅
We believe the next generation of software teams will not be measured by how fast they build. Everyone will build fast. They will be measured by how fast they can trust what they built. 🚀
Would love to hear how your team is dealing with this gap.
Learn more: https://www.testmuai.com/kane-cli-ph/
how is this different from Claude in Chrome?
TestMu AI
@naima_dar Kane-CLI does everything Claude in Chrome does: drives a real browser from natural language, navigates, fills, clicks, verifies. The difference is what it leaves behind.
Claude in Chrome reasons its way through the task every time you ask. Kane does that once, then hands you a deterministic test case: exported code, structured NDJSON, per-step logs and screenshots, all persisted to Test Manager. The next thousand runs replay that artifact instead of re-deriving it. Same result every time, in CI, with a real exit code.
That's the future-proofing. Agentic exploration is how you author the test; determinism is what makes it a regression suite you can trust six months from now.
TestMu AI
Hi, I'm Mudit Singh, Co-Founder of TestMu AI.
The thing I love most about Kane CLI: the whole loop works for everyone.
👨💻 Developers feed it a PRD and get scenarios, runs, and a verdict before the PR
✍️ Business teams can describe flows in natural language and automate the boring browser stuff
🤖 AI agents run it to verify their own work and read the verdict straight from the output
📱 Mobile teams, starting today: point the same commands at Android emulators and iOS simulators
Every run leaves an evidence pack. Every verdict is backed by AC coverage. Nothing rests on "trust me, I checked".
Getting started is the easy part
The Starter plan is free. One install command, npm, brew, or curl, and your first verdict lands in minutes.
Try it, break it, tell us what is missing. Your feedback this week directly shapes the roadmap.
Learn more: testmuai.com/kane-cli-ph
Hi everyone, I'm one of the engineers building Kane CLI. Good to finally have this out in the world.
The part I'm personally most proud of: we built it agent-native from day one. I've spent 2+ years shipping frontend at TestMu AI, and if that taught me anything, it's that writing UI was never the slow part, proving it still works after every change is. AI has made the writing nearly instant, which makes verification the real bottleneck. So we designed for it: every command can emit machine readable output, meaning it's not just humans in a terminal, your coding agent (Claude Code, Cursor, whatever you use) can invoke kane-cli, stream the run, read the verdict, and act on it inside its own loop. AI writes the code, Kane CLI verifies it in a real browser (or on mobile), and the agent gets machine-readable proof back. Closing that loop is what makes autonomous dev workflows actually trustworthy.
The other thing we obsessed over: a pass has to actually mean something. Every verdict ships with an evidence pack; screenshots, console logs, network responses; so a green check is never "the model felt good about it." You can see exactly what was verified, and when something fails you're not guessing.
It's local-first and free to start. Happy to answer any questions in the comments.
Nas.com
How much context can Kane understand from a PRD before generating the actual browser scenarios?
TestMu AI
@nuseir_yassin1 Kane doesn't read the PRD as one giant prompt. Durable context - domain terms, roles, business rules - goes into a project context file that applies to every run. Each scenario is then one objective, with multiple acceptance criteria. The constraint isn't context window, it's decomposition.
The limit isn't how long your PRD is, it's how well it decomposes into self-contained scenarios.
Could developers trigger Kane directly from CI/CD and block deployments automatically when critical browser workflows fail?
TestMu AI
@himani_sah1 KaneCLI can directly run from CI/CD pipelines and allow you to create validation harness. If critical flows break, you changes can be blocked. More information available here: https://www.testmuai.com/docs/kane-cli-cicd
TestMu AI
Hi, I'm Shantanu Wali, Head of AI Products at TestMu AI.
Most tools give you a test runner. We built an assurance loop:
📥 Ingest → your source, your PRD
🧩 Design → use cases, acceptance criteria, test scenarios
▶️ Run → test.md, executed in a real browser or on a mobile device
📸 Evidence → evidence pack for every run
📊 Coverage → how many ACs are covered
✅ Verdict → shipping confidence, backed by proof
Decisions we fought hard for
💻 Local first, running on your own Chrome
💬 Natural language objectives instead of selectors
🔧 Autoheal, so cosmetic UI changes never break a flow
🤖 Agent-native output, so Claude Code or Cursor can call Kane CLI and read the verdict on their own
And starting today, mobile 📱
v0.8.1 makes mobile a first-class platform. Same setup, same sessions, same evidence model, now on Android emulators and iOS simulators. Run devices list, pick a target, and the AI reasons about mobile screens the way it reasons about web pages.
For the skeptics
Hacker Mode exports any flow to native
Playwright code. Never locked in. 🔓
Ask me anything technical, I will be here all day.
Learn more: testmuai.com/kane-cli-ph