CIFuse / developer tools
OPEN SOURCE / OFFLINE BY DESIGN

Less log scrolling.
More shipping.

Your build failed. Your next hour shouldn't.
Turn noisy CI logs into grouped failure signals, exact evidence and a focused investigation plan.

No API keysNo log uploadsZero runtime dependencies
CLI / Node.js 22+npx --yes github:brunnojob/cifuse --demo
01 / FAILURE WORKBENCH

Find your starting point.

● Processed on your device

Build log

5 MiB total · up to 100 files
Compare with a previous report

Logs stay in memory. Common credentials are redacted from reports, but redaction is best effort. Review exports before sharing.

Triage report

Ready
↳

The signal is in there.

Load the example or add a log to find matching failure patterns.

01

Evidence before guesses.

Every signal links to file and line. Suggestions are investigation steps, never a claim that the root cause is proven.

02

Stop reading the same error.

Repeated diagnostics become one group with occurrence counts. Compare JSON reports to spot new and resolved signatures.

03

One engine. Three ways in.

The browser, CLI and reusable GitHub Action share the same deterministic rules. No model, account or backend required.

BUILT IN THE OPEN

Your weird build error belongs here.

Help improve a rule, contribute a sanitized fixture, or tell us where the report missed the useful part.

Share feedback →