Causefile Buy CLI beta

Free public run review · paid CLI for private logs

Find the first useful cause in a failed CI run.

Causefile turns noisy Playwright, npm, typecheck, lint, and dependency failures into a cited likely cause, owner/file hint, and smallest next action.

Send one public failed Actions run to judge fit. Buy the local CLI beta when you want private-log and repeated team use.

Send public run URL See sample output Buy CLI beta
Tests
69/69 passing
Public failed runs
500 processed
Claim support
214/214
Free public-run review. Paid local CLI beta. Send a public GitHub Actions URL and get a report back first. If it is useful, buy the local CLI for private logs and repeated team use. No local model setup required.
  • No GitHub App
  • No account
  • No local model
  • No log upload
  • No telemetry by default
causefile 
$ causefile triage playwright-flaky-test.log
Verdict: actionable
Likely cause: test_failure
Confidence: 0.95
Owner hint: tests/checkout.spec.ts:42
01 Log evidence

Playwright assertion timed out.

02 Cited cause

Button stayed disabled for 15000ms.

03 Next action

Inspect checkout fixture state.

Causefile report

Pay button never becomes enabled

  • Cause Playwright assertion timed out while waiting for the checkout button.
  • Cited lines `Expected: enabled`, `Received: disabled`, `Timeout: 15000ms`.
  • Next action Inspect the payment-ready fixture before changing app code.

Built for the first thirty minutes after red CI

Red CI should not become a 30-minute Slack thread.

See the first cause

Every report points to concrete log lines instead of summarizing the whole failure into vague prose.

Assign the right owner

File, package, and command hints tell the next person where to look before the failure gets bounced around.

Measure what helped

Each run creates a row for `accepted`, `wrong`, or `needs_follow_up` so quality can improve from real failures.

Sanitized sample

What the beta produces.

playwright-flaky-test.log 
1) tests/checkout.spec.ts:42:7 › checkout

Error: expect(locator).toBeEnabled() failed

Locator: getByRole('button', { name: 'Pay now' })
Expected: enabled
Received: disabled
Timeout: 15000ms

actionable · confidence 0.95

Likely cause: test failure

The log points to a failing Playwright assertion. Strongest owner hint: tests/checkout.spec.ts:42.

  1. Open the failing test and assertion.
  2. Confirm whether expected behavior or fixture data changed.
  3. Compare against the last merged change and dependency updates.

Privacy boundary

Private logs stay on your machine.

Local CLI only. No hosted log upload. No telemetry by default.

Reports are best-effort redacted, but generated artifacts should still be reviewed before sharing.

Support asks for safe excerpts or reviewed CSV rows, not raw private logs.

No-install first step

Send one public failed run before installing.

If you want to confirm fit first, send a public failed GitHub Actions run URL for a free first review. You will get back a short report with the likely cause, cited lines, and whether the result was clear enough to justify a local trial.

Send public run URL

Paid beta

EUR 299 for one team/repo, 30 days.

This is paid beta access to the local CLI for private logs and repeated team use. It includes email delivery within 24 hours, quickstart, one optional onboarding call, and support for install, redaction concerns, and wrong triage reports.

  • Try one public run review with no install first.
  • Buy beta access before running npx causefile doctor.
  • Try 3-5 failed logs locally.
  • Return reviewed rows, not raw logs.
  • Refund if it cannot be installed or run in the first week.
Buy CLI beta access Ask for a CI failure review