Account

Account and tokens

Overview

Shows your plan, this month's analyses and fixes against their limits, when they reset, and your recent requests: when each ran, which model answered, whether it succeeded, and whether it counted. On a team, the meters show the team's shared pool.

Teams

Team and BYOK Team plans are shared by up to as many people as the plan has seats. The person who pays is the owner.

The owner opens Team and invites people by GitHub username. Each invitation holds a seat.
The invited person signs in to the dashboard with that GitHub account and accepts the invitation on their Team page.
From then on, their CLI and CI tokens draw from the team's pool. npx kwikqa status shows the team's plan and usage.

Team insights

Insights are off until the owner turns them on from the Team page. While they're on, every CLI on the team shares, after each command:

analyze: the name, file, and Playwright project of each failing or flaky test, and the result;
fix: the test being repaired, whether the patch was applied, declined, or abstained, and how many lines it changed;
validate: whether the repair held or was rolled back.

Nothing else: no evidence, source code, diffs, or error messages, and nothing at all from analyze --local. The Insights page shows everyone on the team the flakiest tests, the fix history, the acceptance rate (patches applied out of those decided), and repair success (repairs that passed validation). Insights are kept for 13 months; the owner can turn them off, or delete everything shared, at any time.

The owner sees each member's analyses and fixes for the month, can revoke invitations, and can remove members; members can leave. To join a team, you can't have a paid plan of your own; cancel it first. Billing belongs to the owner, who adds seats in Billing. If the owner's team plan ends, members return to their own Free plan.

CLI and CI tokens

Every npx kwikqa login creates a token named "CLI sign-in" with the date. You can also create named tokens for CI in Account:

Enter a name that says where the token will live, such as "GitHub Actions", and create it.
Copy the token. It is shown once; KwikQA stores only a hash.
Provide it to the CLI as KWIKQA_TOKEN.

The list shows when each token was created and last used. Revoke any token you no longer use; the CLI using it is signed out immediately. npx kwikqa logout revokes the token of the machine you run it on.

Export your data

Download my data in Account gives you a JSON file with everything the service stores about you: your account, token names and dates, monthly usage, and request records.

Delete your account

Deleting your account cancels any subscription now (an annual plan's unused months are refunded, as in the refund policy) and removes your account, tokens, sessions, team memberships, usage, and request records. Paddle keeps billing records as tax law requires. You can sign in again later to start a new free account.