Early access · invites go out by hand

The AI QA engineer that knows your app end to end.

Describe a test in plain English. Kiwame maps your app, drafts the scenario, waits for your yes, runs it in a real browser and hands you the evidence.

Nothing runs until a human says yesPasswords stay in your keychainReplays cost zero tokens

Kiwame · Northwind Outfitters

about:blank

browser idle

PASS 6/6 video9 screenshotsHARconsolereplay: 0 tokens

How it works

Three things Kiwame does. One thing it never does without you.

It learns the app, writes the test, runs it. The approval in the middle is a hard gate, not a suggestion.

Map

It learns your app and writes the map down.

Kiwame explores the live app read-only, or learns from a document, and keeps what it found as plain markdown in your git repo. Wrong about something? Tell it, and your correction wins.

appmap/
  overview.md
  pages/checkout.md
  flows/sign-in.md

Scenario

One sentence from you becomes a runnable test.

Kiwame reads the map, drafts every step with what to expect, then stops. No agent can approve a scenario, in any mode. It runs only after you have read it and said yes.

$ kiwame plan "the checkout flow"
drafted  checkout/sign-in-and-buy-parka
state    draft → waiting for you

Run

A real browser, every step proved, the evidence kept.

Each expectation is checked on the page, not assumed. You get a verdict per step, screenshots, video, the network calls and the console, filed under the run.

runs/checkout-…/
  results.md      PASS
  steps/          screenshots
  network.har     video/

Evidence

A verdict you can show someone, not a log line you have to trust.

PASS · checkout/sign-in-and-buy-parka · replayed without a model

1	Sign in as demo@northwind.test with <secret>demo_password</secret>	PASS
2	Add the Fjord Down Parka to the cart	PASS
3	Open the cart from the header	PASS
4	Fill the shipping address	PASS
5	Fill the card number 4242 4242 4242 4242	PASS
6	Request permission, then place the order	PASS

✓
Every step proved on the pageText, URL, an element or what a field holds. A step with no passing check cannot be marked passed.
✓
Video, screenshots, HAR, consoleKept with the run. When something fails you see what the browser saw, and which network call broke.
✓
Replay without a modelA passing run becomes a Library test. Same steps, same checks, in seconds, for zero tokens, on every pull request.
✓
Share a run for 30 daysOne link for the person outside the team who needs to see it. Credentials redacted. Revoke it any time.
✓
Tickets in, bugs outPlan from a Jira ticket, or drop a spreadsheet of test cases on the chat and Kiwame turns every row into a scenario.

Try it

Say what you would test. See the scenario Kiwame would draft.

A sketch of the real thing, with no model behind it. On your app Kiwame reads the map first, so the steps name your pages and fields.

scenarios/checkout/apply-coupon.mddraft

Apply a coupon at checkout

Sign in and add any product to the cartEXPECT the cart count shows 1
Open the cart and go to checkoutEXPECT the order total is shown
Enter the coupon code and apply itEXPECT the total drops and the discount line names the coupon
Enter a coupon that does not existEXPECT a clear message and the total unchanged

needs: <secret>shopper_password</secret> · asked once, never shown to the agent

Draft. A human reads it and approves it before anything runs.

Where it lives

One QA engineer, four doors. Pick the one that fits the moment.

The same notebook, scenarios and evidence behind each of them, so a test drafted in the app replays in CI.

The desktop app

Chat with Kiwame, watch the browser live, approve scenarios in a native dialog, read the run. Mac and Windows.

The Kiwame desktop app: a chat on the left, the live browser and run on the right

Inside your coding agent

Claude Code, Cursor or Codex drive Kiwame's tools over MCP. Ask for a check in the middle of a change and get verdicts back in the same conversation.

you:  check the coupon field on localhost:3000 works

kiwame › quick_test(localhost:3000, 3 checks)
  ✓ coupon field accepts SAVE10
  ✓ total drops by 10%
  ✗ bad code shows no message  ← finding

The command line

Plan, approve, run and replay from a terminal, in a git workspace your whole team shares.

$ kiwame crawl https://staging.yourapp.com
$ kiwame plan "sign-in and checkout"
$ kiwame run checkout/sign-in-and-buy-parka
$ kiwame replay checkout/sign-in-and-buy-parka   # no model, free

Your CI

A container image and a GitHub Action. Approved tests replay on every pull request and turn it red or green. Exit codes a pipeline understands.

- uses: kiwame-qa/action@v1
  with:
    suite: checkout

exit 0  all passed
exit 1  something failed  → newly failing, first
exit 2  nothing ran

Guardrails

Three gates that stay human.

Approval

No agent can approve a scenario. Approval is bound to the file's content, so an edited test goes back to draft until a person reads it again.

Permission

Anything irreversible asks first: delete, pay, send, change settings. Denied means that step is skipped and reported, never retried.

Credentials

Kiwame types <secret>name</secret>, never the value. Values live in your OS keychain, bound to the site they belong to, and never reach the agent, the logs or the report.

Two minutes

Watch Kiwame learn a shop, draft a test and run it.

Early access

Get an account when the next batch opens.

We invite a few teams at a time and set each one up personally. Tell us what you test and you move up the list.