The panel

The panel at app.kaab.ist is where people, rather than programs, work with Kaabist: building programs, answering parked jobs, reviewing fixes and managing the organisation. Everything it does goes through the same API your code uses, so what you set up here is what your jobs run with.

When to use it

Use the panel to build and test programs visually, to answer jobs that need a person, to review the healing proposals Kaabist makes, and for account work: members, keys, billing. Use the API, an SDK or the CLI to run jobs from your own systems; the panel shows those jobs too.

Finding your way

The sidebar on the left starts with the organisation switcher: your organisation's name, and a menu listing every organisation you belong to with your role in each, Create organisation and Organisation settings. Below a search button come the pages, in groups:

Pages your role cannot use are not shown. Your e-mail at the bottom of the sidebar opens Profile, Security, API keys, Keyboard shortcuts and Sign out.

The top bar shows where you are as breadcrumbs and, on the right, an N live button whenever live browsers are open (takeovers, builder browsers, pickers, agent browsers), each with Close; then the keyboard-shortcuts button and the light/dark switch. Banners under it say when two-factor authentication is required or credits are low.

Ctrl+K (⌘K) opens the command menu. It lists what you can do on the page you are on first (on a job: run again, copy the ID, cancel), then opens a job or program when you paste its id, then pages. ? lists every shortcut. G then a letter jumps: G H dashboard, G J jobs, G A attention, G R review, G P programs, G K API keys, G M members, G S security.

The panel is dark by default; the switch in the top bar changes it and the choice is remembered.

Working through a list

Every list in the panel (jobs, programs, research, review, attention, sessions, schedules, webhooks, support, the audit log, credits, keys, members) works the same way. Jobs are grouped by status, with what needs a person first: needs attention, awaiting input, running, queued, failed, succeeded, canceled. Other lists group the same way where their records have a status. Click a group's header to fold it. Click a row to open the record; rows without a page of their own (a key, a member) keep their actions in the right-click menu and in Ctrl+K.

Selecting rows shows a bar at the bottom with the actions for all of them. Right-click a row for the same actions with their keys. A group with more jobs than it shows says so (25+); Show more at its end adds the next ones there. On a job's page, R runs it again, and the job's properties (status, program, tier, region, proxy, duration, credits, tags) sit in a column on the right.

The Dashboard greets you by name, names the organisation you are working in, and shows three tiles (jobs in the last 24 hours as succeeded, failed and in progress; jobs that need attention, split into waiting for a value and stopped; credits available and reserved), followed by Get started cards: create an API key, try the API, invite your team, turn on two-factor.

Signing in

Create an account with your e-mail and a password (at least twelve characters, hard to guess), or with GitHub or Google where your deployment offers them. A link sent to your address verifies it; you can also sign in with an e-mailed link instead of a password. Reset your password sends a one-hour link.

Owners and admins need an authenticator app (TOTP) to manage keys, members and billing, after a seven-day grace for a new organisation. Settings → Security sets it up and shows ten backup codes once. Creating, rotating or revoking a key and deleting the organisation also ask for your password or a code when you last entered one more than fifteen minutes ago.

Organisations and members

Every account starts with a personal organisation; create more from the switcher. Settings → Members changes roles (see accounts and roles); Invitations e-mails a seven-day link to the address you enter, and only that address can accept.

API keys and the explorer

Settings → API keys creates keys (shown once), rotates them with a grace period and revokes them (see keys and modes). The API explorer sends any public API operation with a key you paste; the key stays in that browser tab.

Programs

Programs lists your programs with their latest version (and a draft badge when one is being edited), aliases, last run, canary setting and how many fields are drifting. New program starts blank, from a URL, from imported JSON or by recording. A program's page lists its versions, manages its aliases and its canary, and opens the program builder.

Jobs

Jobs lists every run, newest first, filtered by status, program, tag, mode, date, batch or schedule. The filters are in the address, so a filtered list is a link you can share. While a job on the page has not finished, the list refreshes every ten seconds. A job's page shows its status and reason, the program version it ran, the tiers it went through, its region, proxy, duration and credits, and tabs for:

• Result: the data, the raw text when the program keeps it, and each warning with what it means;
• Steps: every step with its timing, screenshot and the stored page it left, which opens read-only with the fields that have ground truth outlined; healing and obstacles in detail;
• Attention / Input: what a parked job is waiting for (below);
• Error: the code, whether retrying makes sense, and the diagnosis;
• Events and Meta: the job's history and its whole envelope.

Re-run creates a new job with the same version and inputs; secret inputs are never shown back, so you type them again. curl copies the request that creates the job, with your key and secrets left as placeholders. A batch's page shows its progress and can cancel the remaining jobs.

Research

Beta, and off in the panel for now: research runs through the API, the SDKs, the CLI and MCP. When it is on, you ask a question and read the result with its sources: a table of the fields you name, passages, a cited report or search results. Research lists every research of the organisation with its question; New research starts one from a form that checks it as the API will and shows what it may cost. See research in the panel.

Attention

Attention lists the jobs that stopped for a person, grouped under their reason ("Waiting for a value", "Blocked by something on the page", "The page changed", "An unexpected page", "Signed out", "Unsure whether a side effect happened") and program, the ones about to expire first. Each card shows the page the job stopped on as a screenshot on the left (click to enlarge) and, on the right, the job, its program, when it expires, what happened, and:

• the platform's proposals, each with Apply and two checkboxes: Promote publishes a new program version with the fix, Remember for this site teaches every program of your organisation to close that overlay; with neither, the fix applies to this job only;
• Take over in a live browser (taking over a job), Skip step, Retry from… a checkpoint (one before a completed side effect is refused), Abort;
• Share resolve link: a hosted page for someone without an account;
• for a job waiting for a value, the form to type it in and Send.

When the same fix is proposed on several jobs of a program, a bar above them offers Apply to all.

Review

Review is the queue of changes the platform proposes: locators the healer relocated, overlays to remember, steps recorded during a takeover. The list shows each proposal's kind and target, the program and version, a confidence bar and its source, filtered by status, kind, source and program. A proposal's page shows the page before and after with the element outlined on each, the locators' diff, the values either side read, the proposed change and the healer's evidence. Approve (a) shows what will change before you confirm, with Promote, Remember for this site and notes; Reject (r) takes an optional reason; Edit candidates corrects a relocation and checks it against the page the job failed on. j and k move through the queue. After a promotion, Run canary now test-runs the new version.

Sessions

Sessions are signed-in browser states your programs start from (options.session). Create one by pasting Playwright's storageState() JSON, or by signing in by hand in a live browser and pressing Save session: only the browser's cookies and storage are kept, sealed with your organisation's key, never shown again. A session's page verifies it now (a credit, five where a browser has to check), sets the refresh program that signs in again when it expires, and its concurrency. A session a job holds cannot be deleted until the job ends.

Schedules

Schedules run a program on a cron in a time zone you choose. The form is built from the program's own inputs and extract fields: pick the fields change detection compares (none means the whole result), what happens when a run is still going or fires were missed, and where runs are reported. The cron is described in words, with its next fires and your plan's shortest interval. A schedule's page lists its runs (each a job) and opens a changed run as sentences ("price changed to 12.5"). Schedules pause when credits run out and resume when they arrive.

Webhooks

Webhooks sends signed HTTPS calls when jobs, schedules, credits or programs change. Add an endpoint with the events it wants (*, job.* or single types) and copy its signing secret: it is shown once. Paste a Discord or Slack webhook address and the endpoint's format switches to a chat message, which those platforms accept; a mismatched one is pointed out and fixed in one click. An endpoint's page sends a test ping and shows the answer, lists deliveries with their answers, latency and next retry, resends one, rotates the secret (the old one keeps signing for a day), and shows how to verify a signature in TypeScript, Python and Go.

BYO providers

BYO providers are your own proxies, language models and captcha solvers. Choose what it is and whose (a single proxy, a list, a vendor's gateway, OpenAI, 2Captcha, …) and fill in the vendor's form; Kaabist tests the provider before saving it, from the network your jobs leave from, and reports the exit address of a proxy. Make one the organisation's default for its kind. A provider a default or an active schedule still names cannot be deleted. BYO needs a paid plan and a verified payment method.

Usage, credits and billing

Usage shows today's jobs, the last week's success rate, the credits available and what waits for a person, then charts over 7, 30 or 90 days: credits by day and tier, finished jobs by outcome, the success rate, browser seconds and proxy traffic, traffic by pool, and the programs and sites that cost most, with the numbers grouped by day, program, tier or tag underneath. Credits lists the balance, the lots it is made of with their expiry, and the ledger, exportable as CSV. Billing (owners and admins) compares plans, buys plans and credit packs through Paddle's checkout, sets auto-recharge, and opens Paddle's portal for the payment method and invoices. When credits run low or out, or a payment fails, every page says so.

Audit log and site profiles

The audit log (owners and admins) lists who did what (keys, members, webhooks, schedules, BYO providers, decisions, takeovers, billing changes) with filters, each entry's details, and CSV of the loaded rows. When Kaabist's team changes something in your organisation (adds or adjusts credits, disables or re-enables it, changes its limits, signs members out, revokes a key) or opens a read-only view of it to help you, the log shows it by Kaabist staff, in plain words such as "Kaabist added 5,000 promotional credits (goodwill)"; the Actor filter can show only those rows. These entries never carry an address or say which member of the team it was. Site profiles shows what Kaabist has learned about a hostname: the tier it needs and how sure that is, the obstacles and API endpoints it knows, when it last blocked.

Worked example

A first tour with a new organisation:

1. On the Dashboard, follow Create an API key and create an sk_test_ key; copy it now, it is shown once.
2. Run a product page such as https://shop.example.com/p/1 with it (see your first job). Open Jobs: the job is at the top, succeeded. Its Result tab shows title "Kulaklık Klasik 101" and price 1337.4 TRY; Steps shows the page it read.
3. Open Programs → New program, choose From a URL with https://shop.example.com/p/1, and continue in the program builder.
4. Press ? to see the shortcuts, then G A: Attention is empty ("Nothing needs you") until a job parks.

Pitfalls

• Working in the wrong organisation. The switcher at the top of the sidebar decides where keys, programs and jobs go; the dashboard names the current one.
• Losing a secret. API keys and webhook signing secrets are shown once. Copy them before you close the dialog, or rotate to get a new one.
• Expecting secret inputs on Re-run. They are never shown back; type them again.
• Missing pages. A page your role cannot use is hidden; ask an owner or admin for a different role.

Reference

• API reference and the API explorer reference
• Roles and key scopes
• Plans