Kane CLI is now an official Kiro Power.
Kiro is @AWS's agentic IDE, and it just opened its Powers ecosystem to bring specialized tooling directly into the agent loop. We're glad Kane CLI is part of that first wave.
Two teams, one idea: developers shouldn't have to leave the place where they build to find out whether what they built holds up.
Kiro brings the spec-driven workflow.
TestMu AI brings the browser.
Together they close the loop inside a single session.
You'll find us in the Powers panel under Kane CLI: Browser Automation and AI Test Authoring, by TestMu AI. One click to install.
Thanks to the Kiro team at AWS for building an ecosystem worth shipping into.
π https://t.co/loneVwnxCg
#Kiro #AWS #KaneCLI #TestMuAI
@narendramodi Going from mitro to friends just to please our generation won't work. The demands remain the same, infact they might even expand.
Mr Dharmendra Pradhan must resign
And if it doesn't happen then, you sir, Mr Narendra Modi also must resign.
#resign_Dharmendra_pradhan#democracy
$ πΊπππ π²π»πΈ --πππ π·πΌπ‘
Put your site, email and price in one file.
kane-cli run "go to {{website}}, assert the price is '{{price}}'" --variables-file vars.json
Reference values with {{blanks}} and keep the real values in vars.json. To test a different site, you change one line in one file. Not every test.
#QA #KaneCLI
Antigravity can build a full Amazon clone from a single prompt. Verifying it works in a real browser is still the hard part. π€
Kane CLI closes that gap. One command, headless Chrome, a 7-step purchase flow validated end-to-end. All 7 steps passed β with results synced to the Test Manager Dashboard.
The agent builds it. Kane CLI proves it works.
Get startedπhttps://t.co/C2MlwrBC6V
#AntiGravity #Google #TestMuAI #KaneCLI
The worst bug in software is the one you can't reproduce.
We built SimForge to kill it: testing inside a deterministic simulation.
Find a bug once β replay it exactly, every time.
API Β· Contract Β· Integration Β· Mutation Β· Exploration.
Get early access: https://t.co/BfMTwGQnNl
Someone built a Salesforce clone with Claude (Fable) in 25 minutes, then verified it end-to-end with Kane CLI in 15. π
Claude tested first with its own in-browser tooling. Good, but the output was walls of text and screenshots buried in a local folder you have to dig up yourself.
Point it at Kane CLI instead, and verification becomes something you can actually read.
Why prefer Kane CLI over in-browser agents:
β Structured pass/fail, not guesswork
β Real assertions (401, "no console errors")
β Console + network checks via DevTools
β Makes and verifies real API calls
β Shareable reports, runs unattended
Why a verification-first agent wins:
βοΈ Evidence you can share, not local screenshots
βοΈ It calls pass/fail, no eyeballing
βοΈ One prompt runs the whole flow, hands-off
βοΈ UI, visual, console, and API in one place
βοΈ Reproducible, auditable runs
Building is fast now. Verification is where you want a specialist.
Point your agent to Kane CLI for agentic verification π https://t.co/PPCu1XI44t
#Claude #Fable5 #KaneCLI
"Register me for TestMu Conf 2026 and download my attendee card."
The most agentic way to register for TestMu Conf 2026 π
One line. Kane CLI filled the form, hit register, and pulled the card in the same session. No clicks. No re-login.
Register now for TestMu Conf 2026 π https://t.co/MXV7kvDxt1
#BrowserAutomation #KaneCLI
$ πΊπππ π²π»πΈ --πππ π·π·π‘
Pick the right mode. Action does the task. Testing grades it.
kane-cli run "fill the signup form" --mode action
Use action when you just want something done. Use testing when you want a strict pass-or-fail gate. Testing turns every check into a hard assertion, so do not reach for it when you only meant to click around.
#KaneCLI
Kane CLI gives your agent eyes. ποΈ
One command, agent mode:
β¨οΈ kane-cli run "go to localhost:3000, click Buy Pro, assert the total due today shows $19.00" --agent
Kane CLI spins up real Chrome, clicks through to checkout, and makes the call. Advertised $19. Charged $29. Failed, with a report you can share.
Gemini CLI takes that report, opens page.js and checkout/page.js, finds the hardcoded $29, and patches it. A second Kane CLI run checks the fix.
β Pass.
A hardcoded value is the easy case. A price pulled from an API. A coupon that applies on render. An overlay covering the total. None of that lives in the code. The browser is the only ground truth.
Reasoning plus verification. The loop closes itself. Write, test, fix, verify, all in one terminal.
Explore now π https://t.co/BWx11SuOjW
#GeminiCLI #KaneCLI
$ πΊπππ π²π»πΈ --πππ πΆπΎπ‘
Keep credentials out of your objectives. Pass them as variables and reference with {{key}}.
kane-cli run "log in with {{email}} and {{password}}" --variables-file creds.json
Mark secrets with "secret": true so they never get committed. Same flow runs on dev, staging, and prod, only the values change.
#KaneCLI
Before a PR goes up, the feature should already be verified in a real browser, locally, before anyone reviews it.
Here is what that catches.
A user clicks "New project", types a name, hits Create. The modal closes. Looks done. Kane CLI watches the sidebar instead, and the new project never appears. Run failed.
The replay points straight at the create-project flow. π
The project was built in memory, then dropped before it ever rendered. The code ran. The modal closed. Nothing threw an error. The UI was still wrong. That is the gap a passing unit test never sees.
Fix it. Run the check again. Green. β
Now the PR goes up, already verified in a real browser. Not caught in review. Not in staging. In the loop, before.
One objective in natural language. Pass or fail out.
Try it on your own pre-PR loop π https://t.co/C8OZYW9e1K
#AIAgent #KaneCLI
THE VERIFICATION
Try Kane-CLI now:
https://t.co/Jx0SPsNxXU
https://t.co/0mCGCeqmyD
Sanket Shah, I loved the way @invideoOfficial has evolved. Brilliant platform.Β β€οΈ@_sankyy
$ πΊπππ π²π»πΈ --πππ πΆπ½π‘
Headless CLI mode, you pass the objective straight into the command: kane-cli run "...". One line in, a real browser verdict out.
π Repeatable by design. Arrow up, hit enter, run the same flow again in a second. Same command, same objective, no drift between runs.
#AIAgents #KaneCLI
Use Kane CLI in Claude Managed Agents.
Kane CLI already runs in Claude Code. Now add it in Claude Managed Agents too.
The same agent that builds a feature can open a real browser and verify it. Pass or fail, with a shareable link.
Set it up now:
β Create an environment and install kane-cli
β Store creds in a Claude credential vault. The agent never sees the values
β Define the agent in one line: run browser tests, report pass or fail
β Give it a URL and a flow in natural language
Try it π https://t.co/xCmvimlgNx
Wired Kane CLI into GitHub Actions today. A little obsessed. π
Now every push runs my critical browser flows against the live deploy.
Removes an entire category of "did we break checkout again?" anxiety.
Try Now πhttps://t.co/1pGjiYDGkc
#KaneCLI