Product · Builder

Click through it once.It becomes a program.

Record the task in a live Kaabist browser, pick the data you want, and edit the steps and the JSON side by side. Test any step against the real site before you publish. No agent and no code needed, and nothing hidden when you want them.

Start free Read the docs

product · builderloop

new program ·BlankURLImport JSONRecord

portal.example.com/invoices

[email protected]

••••••••

Invoices

INV-1042€1,240.00
INV-1043€318.50
INV-1044€2,075.00

select similar · 3 rows

supplier-invoices · steps ⇄ jsondraft@1 · published

gotoportal.example.com/login
fillEmail ← inputs.email
fillPassword ← secret input
clickSign in
extractinvoices[] · invoice, total

{ "goto": "https://portal.example.com/login" },{ "fill": { "role": "textbox", "name": "Email" },  "value": "{{inputs.email}}" },{ "fill": "#password", "value": "{{inputs.password}}" },{ "click": { "role": "button", "name": "Sign in" } },{ "extract": { "invoices": { "selector": "tbody tr",  "many": true, "fields": { "total": { "type": "money" } … } } } }

✓ lint · ✓ run to here · dry run

[{ "invoice": "INV-1042", "total": 1240, "currency": "EUR" }, … 3 items]

How it works

01
Record, don’t write
The recorder watches what you do in the live browser: it saves each click and field as a step with several locators to fall back on, turns password values into secret inputs, suggests a wait for a one-time code, and proposes checks that the page looks right.
example
```
goto     portal.example.com/login
fill     Email      ← inputs.email
fill     Password   ← inputs.password (secret)
click    Sign in
await    one-time code (hosted page)
extract  invoices[] · invoice, total (money)
```
02
Pick data like a person
Hover to highlight, click to pick. Select similar builds a list from one example, you can move to a parent or child element, and Ctrl-click freezes a menu that only shows on hover. On a stored page, the snapshot picker builds the fields without running the site again.
example
```
"invoices": {
  "selector": "tbody tr", "many": true,
  "fields": {
    "invoice": "td:nth-child(1)",
    "total": { "selector": "td.total", "type": "money" }
  }
}
```
03
Three control nodes, not a canvas
A program stays a readable list: when for a condition, loop until for a repeat, paginate for the next page. The same JSON goes to the API, the CLI and your agent, so a program built here can be pulled into git and pushed back.
example
```
$ kaab programs pull supplier-invoices
$ kaab programs diff supplier-invoices.json
$ kaab programs push supplier-invoices.json
```

Questions

You were going to ask.So here’s the answer.

No. Record the task, pick the data, test it and publish. The JSON is there when you want to read or change it.

Yes. They all edit the same program. Your agent can draft it, you can fix a step in the builder, and a teammate can push the next version from git.

Never into the program. A password you type while recording becomes a secret input, given at run time and kept out of logs, snapshots and screenshots.

More of Kaabist

Resumes where it stopped
Some steps only you can finish: a one-time code, a captcha, an approval. Kaabist pauses the run right there and emails a link to you, or to the teammate or customer you choose. Once they answer, the program continues from its last checkpoint. Nothing starts over.
Read more about Resumes where it stopped
Built by your coding agent
Connect Claude Code, Codex or Cursor to mcp.kaab.ist. Your agent opens a real Kaabist browser, works through the site with you, and what it does becomes a program: versioned, linted, and tested with a dry run before it ever submits anything.
Read more about Built by your coding agent
Never submits twice
Mark the steps that change something (a submit, a payment, an order) as side effects. Kaabist writes each one down just before it runs and again once it has worked. If a server crashes in between, Kaabist never presses the button again on its own: it pauses and asks you to check.
Read more about Never submits twice

Stop fixing selectors.Ship the automation.

Start free Read the docs

Click through it once.It becomes a program.

Record, don’t write

Pick data like a person

Three control nodes, not a canvas

You were going to ask.So here’s the answer.

Do I need to write code?

Can I mix the builder with my coding agent or the CLI?

Where do passwords go?

Resumes where it stopped

Built by your coding agent

Never submits twice

Stop fixing selectors.Ship the automation.