Troubleshooting

Use this page when Ernest appears installed but pull requests are not being reviewed.

ernest command is not found

The installer prints the directory where it placed the binary. Make sure that directory is on your PATH.

For the default local install location:

export PATH="$HOME/.local/bin:$PATH"

Then retry:

ernest --version

CLI authentication fails

Run device authentication again:

ernest auth login

Use the GitHub account that can access the Ernest organization or account you want to inspect. If GitHub rejects the device flow, confirm the Ernest GitHub App has Device Flow enabled.

CLI refuses untracked files

Ernest blocks unexpected untracked files so temporary folders, generated files, or local secrets are not uploaded by mistake.

If the file belongs to the change, add it intentionally:

git add path/to/file
ernest inspect .

If the file does not belong to the change, delete it or add it to .gitignore.

CLI context is too large

Large generated files, dependency folders, snapshots, or temporary artifacts can make the hosted inspection context too large.

Check what changed:

git status --short
git diff --stat

Then remove or ignore generated artifacts before retrying.

CLI cannot find the Ernest account

The CLI can only inspect repositories that belong to an Ernest organization or account your authenticated GitHub user can access.

Open the dashboard, select the owning organization or account, sync repositories, and enable the repository. Then rerun:

ernest inspect .

Repositories do not appear

Open the GitHub App installation and confirm the repository is selected. Then click Sync repositories in Ernest.

If the organization has never synced repositories before, returning from GitHub setup should trigger the first sync automatically. If it does not, click Sync repositories once.

Pull requests are not inspected

Check these conditions:

• The repository is selected in the GitHub App installation.
• The repository is enabled in Ernest.
• The organization has remaining Free bonus quota, Dev/Pro monthly quota, or Enterprise unlimited quota available.
• The pull request event came from the same organization or account selected in Ernest.

If a gate blocks the inspection, Ernest should post a clear blocked status instead of consuming quota.

GitHub setup returns to GitHub

Confirm the GitHub App setup URL points to:

https://ernest.kubeply.com/github/setup

If GitHub redirects to the GitHub installation settings page, manually open Ernest with the installation ID:

https://ernest.kubeply.com/github/setup?installation_id=<installation_id>

Then fix the GitHub App setup URL before inviting other users.

Billing actions do not open

If checkout or the customer portal does not open:

• confirm the selected organization is the one you expect in the sidebar
• confirm the account has admin access for that organization in Ernest
• retry from the billing page
• contact support with the organization name and the timestamp

Ernest posts no inline comments

Some findings cannot be attached inline when GitHub rejects the line range. In that case, the finding should still appear in the review summary.

If neither inline comments nor a summary appears, check the GitHub check status first. The check should explain whether the review completed, failed, or was blocked.

Ernest appears stuck

An inspection can be delayed if sandbox preparation, model calls, or GitHub API calls fail. If a check stays in progress for more than a few minutes, contact support with:

• repository name
• pull request number
• latest commit SHA
• approximate time the pull request was opened or updated

Need help

Contact [email protected].