# Troubleshooting (https://luxor.ai/docs/reviewer/troubleshooting)

> For the complete documentation index, see [llms.txt](https://luxor.ai/llms.txt)

Diagnose Code Reviewer GitHub App access, review triggers, large pull requests, and repository settings.

If Code Reviewer isn't behaving as expected on a repository, the cause is almost always one of three things: the Luxor Agent Cloud app can't access the repo, the pull request is too large for a single pass, or a setting is scoped differently than you expect. Work through the sections below in order; most issues are resolved by re-scoping or reinstalling the app from **Code Reviewer → Configuration → Connections**.

## Code Reviewer does not respond to `@luxor-reviewer`

Code Reviewer uses its own app: the separate Luxor Code Reviewer GitHub App on GitHub, and the Luxor Agent Cloud app on Cursor Origin. It does not require a GitHub Actions workflow or an API key in repository secrets. Confirm that the app can access the repository, then comment `@luxor-reviewer` on the open pull request. If the app is missing or its repository selection is stale, update or reinstall it as described in [Manage Connections and Repositories](https://luxor.ai/docs/reviewer/repo-management.md).

## Code Reviewer isn't running on a repository at all

If reviews never appear on a repo's pull requests, the repository is likely not accessible to Code Reviewer. Confirm the repo is included in the app's access list in GitHub or Cursor Origin, then reinstall the integration if needed. See [Manage Connections and Repositories](https://luxor.ai/docs/reviewer/repo-management.md) for how repository access is granted and kept in sync.

Also check that [Automatic Review](https://luxor.ai/docs/reviewer/settings.md#automatic-review) is on for that repository, and that the author isn't in [Ignore Usernames](https://luxor.ai/docs/reviewer/settings.md#ignore-usernames). Draft pull requests are reviewed once they're marked ready for review.

## Code Reviewer isn't reviewing Cursor Origin pull requests

* **The connection isn't active.** Open **Code Reviewer → Configuration → Connections** and check that Cursor Origin shows **Connected**. Use **Reconnect** or **Retry install** if it doesn't.
* **The repository is a GitHub mirror.** Mirrors keep using GitHub; connect GitHub to review them.
* **The pull request was reopened.** Reopened pull requests aren't reviewed automatically. Mention `@luxor-reviewer` to request a review.

See [Cursor Origin](https://luxor.ai/docs/reviewer/cursor-origin.md) for how the connection works.

## The Luxor Code Review check fails on Cursor Origin

On Cursor Origin, the **Luxor Code Review** check fails while Critical, High, or Medium findings are open on the pull request, including findings from earlier reviews. Fix the findings, or dismiss the ones that don't apply by replying in the finding's thread with a phrase such as "false positive" or "won't fix". See [Dismiss a finding](https://luxor.ai/docs/reviewer/cursor-origin.md#dismiss-a-finding).

## CI not running on Code Reviewer’s commits

Ensure you’re using the GitHub App or custom app (not Actions user), check workflow triggers include the necessary events, and verify app permissions include CI triggers.

## "Context Window Exceeded" or Missing Files

The Pull Request is too large. Most AI models have a limit on the number of lines or files they can process in a single pass.
Break down large PRs into smaller, more manageable chunks.
Use an ignore list (e.g., .ai-ignore) to exclude auto-generated files, lockfiles (package-lock.json), or documentation.

## Reviews feel too noisy or miss the things you care about

Code Reviewer can be tuned per repository. If it's flagging things you don't care about, or missing your team's conventions, describe your standards, focus areas, and what to ignore in the repository's `AGENTS.md` or `CLAUDE.md`. See [Custom Context](https://luxor.ai/docs/reviewer/custom-context.md).

## Frequently asked questions

**Why did the reviewer skip my pull request?**
The most common causes are that the repository isn't connected (see [repository access](https://luxor.ai/docs/reviewer/repo-management.md)), the author is in Ignore Usernames, or the PR exceeded the model's context window. Splitting a very large PR into smaller ones usually resolves it.

**Can I control which files are reviewed?**
Yes. Use an ignore list to exclude generated files, lockfiles, and vendored code, and use [Custom Context](https://luxor.ai/docs/reviewer/custom-context.md) to point the reviewer at high-risk areas.

**How do I re-run a review?**
Comment `@luxor-reviewer` on the open pull request.

Still stuck? Reach out to us at [hello@luxor.ai](mailto:hello@luxor.ai) or use the in-app chat (see image below).

<img src="getAsset(&#x22;/images/reviewer/troubleshoot.png&#x22;)" alt="In-app support chat for Code Reviewer troubleshooting" className="w-full object-contain md:w-3/4" />

<img src="getAsset(&#x22;/images/reviewer/fernand.png&#x22;)" alt="Support chat conversation" className="w-full object-contain md:w-1/4" />