GitHub Actions
Your build broke on
line 1,240 of 3,880.
Debug Assistant reads the log for you, finds the line that actually failed, and tells you what to change. Connect a repository and the next red build explains itself.
Free and self-hostable. Reads logs, never your source.
How it works
-
01
Connect a repository
Sign in with GitHub and pick a repository. Debug Assistant adds a webhook so it hears about finished workflow runs.
-
02
A run fails
GitHub sends the run. Debug Assistant downloads the logs for the jobs that failed and scans them against its ruleset.
-
03
Read the diagnosis
You get the failing line, what category of failure it is, and the fix — instead of 4,000 lines to scroll through.
What it recognises
Pattern matching, not a language model. The same log always produces the same diagnosis, there is no API key, and nothing is sent anywhere.
-
Dependency failures
Missing packages, versions that do not exist, lockfile conflicts, registry errors.
-
Test failures
The assertion that failed and the test that owns it, picked out of the runner's output.
-
Compilation errors
Type errors, syntax errors, and unresolved imports with the file and line.
-
Configuration and secrets
Missing environment variables and unset secrets, which read as unrelated crashes.
-
Timeouts and limits
Jobs killed by the runner, out-of-memory kills, and steps that ran out of time.
-
Infrastructure
Runner failures, network errors, and rate limits — the failures that are not your fault.
Stop reading logs.
Sign in with GitHubDebug Assistant asks for repository access so it can read workflow logs and add a webhook. You can disconnect a repository at any time, which removes the webhook too.