Help

Troubleshooting

Every command ends with a line like Result: repair-failed (validation-failed): the outcome, then the reason code in brackets. The record path printed after it has the full detail.

Outcomes

Outcome	Meaning	Exit
`diagnosed`	At least one cause is supported by the evidence.	0
`inconclusive`	The evidence doesn't support a cause, or the run couldn't be analyzed.	0
`proposal-ready`	A repair was proposed with `--propose-only`.	0
`repair-declined`	You declined a request or the patch.	0
`abstained-from-repair`	KwikQA chose not to repair, for the reason given.	0
`awaiting-validation`	The patch is applied. Run `validate`.	0
`repaired`	Validation passed and the patch was kept.	0
`repair-failed`	Validation failed and the patch was rolled back.	1
`validation-unavailable`	The repair couldn't be validated, so it wasn't kept.	1
`operation-failed`	Something outside the normal flow failed. See the reason code.	1

Common reason codes

Reason	What to do
`report-unavailable`	No report was found. Add the JSON reporter, or pass `--report`.
`report-unreadable`	The report isn't valid Playwright JSON. Rerun the tests so the reporter writes it in full.
`no-failures`, `zero-tests`	The report has nothing to diagnose.
`interrupted-run`, `report-errors`	The run didn't finish cleanly, so its evidence isn't trustworthy. Fix the run, then analyze again.
`evidence-budget-exceeded`	The evidence wouldn't fit the packet size limit. Analyze a report with fewer failures.
`remote-consent-declined`	You declined the preview. Nothing was sent.
`application-owned`, `environment-owned`	The evidence points outside your tests. Use the diagnosis to investigate; no repair is proposed.
`repair-config-missing`, `repair-config-invalid`	Run `npx kwikqa init`, or fix `kwikqa.config.json` using the message.
`repository-status-unavailable`	KwikQA couldn't read git status. Run it inside the git repository, with git installed.
`original-test-ambiguous`	The failing test couldn't be identified uniquely. Analyze a report with fewer failures.
`validation-scope-unavailable`	KwikQA couldn't work out which tests the change affects, so it didn't apply the patch. The message says why.
`baseline-capture-unavailable`	The repair changes shared test code, which 0.1 can't validate yet. See the known limitation.
`application-rejected`	KwikQA couldn't prepare or apply the patch safely, for example because a target file changed. The message says why; run `fix` again.
`application-recovery-required`	KwikQA found patch records in `.kwikqa/` it can't reconcile. The message names the problem; check the patched files with `git diff` before you continue.
`no-pending-repair`	There is no applied patch to validate. Run `fix` first.
`validation-incomplete`	A required check was skipped, interrupted, or didn't produce fresh results. The patch was rolled back.
`rollback-conflicted`	You edited a patched file after KwikQA applied it, so rollback stopped instead of overwriting your work. Review the file by hand.
`no-retry-available`	The one retry was already used. Fix the test by hand.

Common messages

Not signed in. Run npx kwikqa login first.: Sign in, or set KWIKQA_TOKEN. In CI, check that the secret is passed to the step.
You have used all … on the … plan: You've reached a monthly limit. See Plans and usage.
Sending evidence needs approval: There is no terminal to approve the preview. Pass --yes, or use --local.
kwikqa fix needs a terminal: Applying a patch always needs a person. Run fix locally.
The bring-your-own-key plan needs OPENROUTER_API_KEY: Export your OpenRouter key in the shell that runs KwikQA.

Still stuck? Contact support.