> ## 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.

# Trigger a code review

> Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.

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.

## Run a code review

Qodo can review pull requests **automatically** or **manually**. Both approaches produce the same review experience and findings, and both are fully configurable. The difference is when and how the review is triggered. See the [**Configuration**](/install-and-configure/configuration-overview) fundamentals for details.

### Run reviews automatically

Automatic is the default. Qodo runs a review as soon as a pull request is opened, reopened, or marked ready for review, without any manual trigger.

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
* Keep review feedback in sync with the latest code changes

Optionally, enable [Review every push](/install-and-configure/configuration-overview/portal-configuration#code-review) to 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)).

Automatic reviews are ideal for teams that want:

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

### Run a review manually

Request a review on demand at any time by adding a comment to the pull request, regardless of your **Code review trigger** setting:

```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 requests 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

To rely on manual requests only, and stop automatic reviews from running at all, set [Code review trigger](/install-and-configure/configuration-overview/portal-configuration#code-review) to **Manual only** in the Qodo portal, or using the `.pr_agent.toml` file.

<Note>
  Re-running a review does not clear findings from previous runs. Qodo automatically strikes through a finding once it's resolved or no longer relevant due to code changes, such as a fix made in a related repository. You can dismiss any other finding manually.
</Note>

### What to expect while a review runs

While a review runs, Qodo posts a temporary "review in progress" comment so you know it's processing the request. Review time varies depending on the size of the pull request, but typically takes a few minutes. The comment is removed once the review is posted, or updated if the run fails or is superseded by a newer run. Admins can disable this with the [In-progress comment](/install-and-configure/configuration-overview/portal-configuration#code-review) setting.

## Next steps

* [Anatomy of a finding](/code-review/comment-anatomy): See what a finding looks like and what each part means.
* [Chat with Qodo](/code-review/chat-with-qodo-in-your-pull-requests): Ask questions or request changes directly in the review thread.
* [Remediate findings](/code-review/remediate-findings-in-prs): Let Qodo generate and apply a fix.