> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Qodo in pull requests

> This guide explains how to use Qodo in pull requests, how reviews run, what you'll see, and how to interact with review feedback as a developer.

Qodo works directly inside your Git provider and integrates into your existing pull request workflow. You can start using it immediately with default behavior, and customize it later as needed.

## What can you configure

Qodo works out of the box with sensible defaults, but its behavior can be customized to match your team's standards and workflows.

Configuration controls things like:

* When reviews run (manual or automatic)
* Where feedback appears (summary, inline, or both)
* How strict or verbose reviews should be
* What content should be ignored

For a full breakdown of configuration options, file locations, and precedence, see the [**Configuration**](/code-review/get-started/configuration-overview) fundamentals guide.

## Run a code review

Qodo can review pull requests in two ways: **manually** or **automatically**. Both approaches produce the same review experience and findings. The difference is when and how the review is triggered.

<Note>
  While a review runs, Qodo posts a temporary "review in progress" comment so you know Qodo is processing the request. The comment is removed once the review is posted. If the run fails or is superseded by a newer run, the comment is updated to reflect the change. Admins can disable this with the [In-progress comment](/install-and-configure/configuration-overview/portal-configuration#code-review) setting.
</Note>

<Tip>
  **Reviewing a pull request that depends on another repository?**

  If your change has a related pull request or branch in another repository, include the related pull request URL or branch name in your pull request description or a linked ticket. This lets Qodo's cross-repository review compare against the right code instead of the related repository's main branch. See [Cross-repository code review](/governance/cross-repo-code-review).
</Tip>

### Run a review manually

You can request a review directly from the pull request by adding a comment:

```bash theme={null}
/agentic_review
```

When you post the comment:

* Qodo acknowledges the request with a 👀 reaction
* The review is generated and posted directly in the pull request
* Feedback appears based on your configuration (summary, inline, or both)

Manual reviews are useful when:

* You want to review on demand
* You're testing configuration changes
* You don't want reviews to run on every pull request update

<Note>
  Re-running a review does not clear findings from previous runs. When Qodo detects that a finding has been resolved, it strikes through the finding. Findings that are no longer valid for other reasons, such as a fix made in a related repository, are not struck through and remain until you dismiss them manually.
</Note>

### Run reviews automatically

Qodo can also run reviews automatically when pull requests are opened or updated.

Automatic reviews are controlled by the [Code review trigger](/install-and-configure/configuration-overview/portal-configuration#code-review) setting in the Qodo portal, or using the `.pr_agent.toml` file, and allow Qodo to:

* Run reviews when a pull request is opened, reopened, or marked ready for review
* Optionally, update the existing review comment on every new commit pushed to the pull request, instead of only at publish time (see [Persistent review comments](/code-review/persistent-review-comments))
* Keep review feedback in sync with the latest code changes

Automatic reviews are ideal for teams that want:

* Consistent review coverage
* Less manual intervention
* Faster feedback loops

Automatic behavior is fully configurable. See the [**Configuration**](/code-review/get-started/configuration-overview) fundamentals for details.