Contact support

Tell us what you were trying to do and what happened. We reply by email.

Get started
Troubleshooting

Find your error message

Look up the exact message you're seeing, what it means, and what to do.

Search this page for the message you're seeing (⌘F or Ctrl+F). If it isn't listed, or the fix doesn't work, contact support.

Signing in and joining

MessageMeaningDo this
Lighthouse is invite-only during our pilot.You opened the sign-up page without an invitation.Ask your team admin for a join link. To start a new team, contact RewareLabs.
A join, invite, reset, or verify link is invalid, used, or expiredThese links work once and expire.Ask for a new link, or request a new password reset.
Your team has reached its 5-member limit during the pilot.The team is full. Pending invitations count.An admin revokes an unused invitation or deactivates someone.
Your account is lockedToo many wrong passwords.Wait a few minutes, or reset your password.

GitHub and repositories

MessageMeaningDo this
Connect a Git provider or GitHub not connectedYour team hasn't connected GitHub.An admin connects GitHub.
Installation pausedThe Lighthouse app is suspended on GitHub.Re-enable it in the app's GitHub settings.
That GitHub installation is already connected to another Lighthouse team.The app on that account belongs to another team.Disconnect it from the other team first.
GitHub sent your install request to the account owner.You can't install apps on that organization.An owner approves the app. Then connect again.
A repository is missing from the listThe GitHub App can't see it.Give the app access on GitHub, then press Sync under Settings › Git providers.
Ask an admin to grant access to a repository.You don't have access to any repository.Ask an admin for repository access.
A branch is tagged Not on GitHubThe branch was deleted on GitHub.Archive or delete it in Lighthouse if you don't need it.

Ingestion

MessageMeaningDo this
Nothing has changed since the last ingestion.That commit is already ingested.Nothing. The cards are current.
This repository already has an ingestion in progress.One ingestion runs at a time per repository.Wait for it to finish.
Ingestion failedThe run stopped with an error.Press Re-run ingestion. See When an ingestion fails.
Latest ingestion failed · using previous cardsThe newest run failed. Earlier cards are still in use.Re-run the failed ingestion.
Interrupted by a backend restart.Lighthouse restarted during the run.Press Re-run ingestion.
OutdatedThe branch has newer commits than the last ingestion.Run an ingestion when convenient.
Credits not enough for ingestion.The team is low on credits.See When you run out of credits.

CLI and pre-commit scans

MessageMeaningDo this
command not found: reware-lighthouseThe CLI isn't on your path.Run uv tool update-shell. Open a new terminal and restart your agent.
The CLI rejects your keyThe key is mistyped, rotated, revoked, or expired.Run reware-lighthouse login again. If that fails, ask an admin to rotate the key.
A message asking you to upgradeThe CLI is too old.uv tool upgrade reware-lighthouse or pipx upgrade reware-lighthouse.
A warning that the config file isn't privateOther users can read ~/.config/lighthouse/config.env.chmod 600 ~/.config/lighthouse/config.env
lighthouse: could not identify a project.The CLI can't tell which repository this is.Run reware-lighthouse init, or pass --repo owner/name.
The repository isn't registeredIt hasn't been added to Lighthouse.Ask an admin to add it.
✗ commit blocked by the repository's scan policy.A finding reached your blocking policy.See When your commit is blocked.
lighthouse: scan skippedUsually out of credits. The commit went through.See When you run out of credits.
lighthouse: scan request failed: …Lighthouse couldn't be reached, or timed out. The commit went through.Check your network. See When Lighthouse can't scan.
lighthouse: no staged files to scan.Nothing is staged.git add your changes first.
The hook doesn't runThe repository uses a shared hooks path or the pre-commit framework.Add reware-lighthouse scan to that hook. See Shared hooks.

Pull request scans

MessageMeaningDo this
This check failed because the repository blocking policy was reached.A finding reached your merge policy.Open the scan, fix the findings, and push.
Lighthouse could not complete the scan. The check did not block this change.The scan failed.Press Rescan in Lighthouse, or re-run the check on GitHub.
This pull request has merge conflicts.The scan is on hold.Resolve the conflicts, or press Scan anyway. See Merge conflicts.
A scan of this pull request is already running.One scan runs at a time per pull request.Wait for it to finish.
No Lighthouse check appearsAutomatic scans are off, the pull request is a draft, or the app can't see the repository.Check the repository's pull request settings and the app's access on GitHub.
The check failed, but the merge button still worksGitHub doesn't require the check.Make the check required.

Credits

MessageMeaningDo this
Your team has no active plan.No plan is assigned.Contact RewareLabs.
Your team has reached its monthly credit limit.This month's credits are used up.Wait for the 1st, or contact RewareLabs.
This API key has reached its monthly credit cap.Your key's cap is used up.Use another key, or ask an admin to raise its cap.

Prompt enhancement

ProblemDo this
/lighthouse-enhance isn't availableRun reware-lighthouse init in the repository, then restart your agent.
The agent says Lighthouse isn't configuredRun reware-lighthouse login, then reware-lighthouse init.
The agent stops and asks whether to continueEnhancement failed. Read the reason, fix it, and ask the agent to retry. Or tell it to continue without enhancement.
Still stuck after reading this page?

Contact support

Tell us what you were trying to do and what happened. We reply by email.

On this page