Skip to main content
When a PR review is missing or unexpected, start with the repository state, the event that should have started the review, Dashboard Activity, and the resulting GitHub output. Check those before changing review policy.

​
Start with Dashboard Activity

Open Dashboard > Activity and find the request:
  1. Choose a time range that includes the pull request event or explicit request.
  2. Filter to GitHub, Daemon, and pr-review, or search for the repository.
  3. Follow the source link back to the pull request and compare the timing with GitHub.
Activity can confirm that Charlie handled the request and identify whether it ran as a daemon or an agent task. It does not explain which lanes applied or why a particular finding did or did not qualify. If the request appears as Agent even though pr-review is installed, confirm that the daemon files reached the default branch and that the comment explicitly asked Charlie for a review. If the files and request are correct, contact support.

​
Charlie did not review the pull request

Check these in order.

​
Confirm that the daemon is on the default branch

Charlie loads DAEMON.md and its lane files from the repository’s default branch. Files that exist only in an installation or configuration pull request are not used. After the files reach the default branch, allow a few minutes for Charlie to load the policy. Installation does not start reviews for pull requests that were already open.

​
Confirm that a matching event happened after Charlie loaded the policy

The reference policy starts a review when:
  • A non-draft pull request is opened.
  • A draft pull request is marked ready for review.
  • CharlieHelps is requested as a reviewer.
  • A pull request comment requests a review from CharlieHelps.
The reference policy does not review every new commit. For an already-open pull request or a follow-up review, request CharlieHelps as a reviewer or leave a clear comment such as:
If your repository uses different watch conditions, compare the event with the current policy on the default branch.

​
Check the pull request and repository

Confirm that the pull request is open and ready for review and that the Charlie GitHub integration still has access to the repository, including that @charliehelps has been invited as a collaborator on the relevant repository or organization.

​
Policy changes are not taking effect

PR review policy only takes effect from the default branch. To prevent a change from defining the rules used to judge itself, Charlie does not run a daemon-powered review on a pull request that changes DAEMON.md or reference Markdown for the pr-review daemon. Merge the policy change, allow a few minutes for Charlie to load it from the default branch, and then exercise it on a separate pull request with a new matching event or explicit request.

​
Activity exists, but GitHub output is unexpected

The reference policy has two normal visible results:
  • When useful findings qualify, Charlie submits one COMMENT review.
  • When every applicable lane completes with no useful finding and no coverage limitation, Charlie leaves exactly one +1 reaction on the pull request body.
A clean review does not produce an empty formal review, top-level comment, summary, praise, or LGTM. Check the pull request body reactions as well as the review timeline. If Dashboard > Activity shows that the task needs attention, follow its source link and confirm that the pull request is still open, ready for review, and accessible. If Activity and the current GitHub state do not explain the missing result, contact support rather than weakening the evidence bar or adding execution instructions to DAEMON.md.

​
The review ran, but its behavior was wrong

Edit the smallest customer-owned policy surface that controls the behavior. See Configure PR reviews for examples. Charlie owns running the review and delivering its GitHub output. Do not try to repair those behaviors by adding orchestration or publication instructions to repository policy.

​
Get help

If these checks do not explain the behavior, email support@charlielabs.ai with:
  • The GitHub pull request URL and repository.
  • The approximate time of the event or explicit request.
  • What you expected to happen.
  • What happened instead.
  • The smallest relevant watch or policy excerpt, when configuration may be involved.
Do not include credentials or private provider configuration.