How these settings are applied
The Portal Configuration page is applied only when no configuration is defined in the repository wiki, the repository root, or the organization settings repository (pr-agent-settings).
For full details about configuration precedence, see the Configuration Overview.
Review settings
This section controls how Qodo performs code reviews, generates PR summaries, and displays findings in pull requests.Code review
| Setting | Description | Options |
|---|---|---|
| Code review trigger | Determines when Qodo runs an AI code review. | • Manual only: Reviews run only when triggered manually using /agentic_review • Published PRs: Reviews run automatically when a PR is published • Draft & Published PRs: Reviews run automatically for both draft and published PRs |
| Comment type | Controls how findings are posted in the pull request. | • Summary only: All findings appear in a single summary comment • Inline only: Findings are posted directly on relevant lines of code • Summary & Inline: A summary comment is posted and findings are also added inline |
| Inline comment threshold | Determines which severity levels generate inline comments. | • High: Only high-severity findings appear inline (all findings still appear in the summary) • Medium: Findings above medium appear inline • Low: Findings above low severity appear inline |
- High findings indicate issues that require action.
- Medium findings are generally recommendations.
- Low severity findings are informational.
PR summary
| Setting | Description | Options |
|---|---|---|
| PR summary trigger | Determines when Qodo generates an AI-powered PR summary. | • Manual only: Generated using /agentic_describe • Published PRs: Generated automatically when a PR is published • Draft & Published PRs: Generated for both draft and published PRs |
| PR summary location | Controls where the generated summary appears. | • Native git description: Replaces the native PR description for the Git provider • Standalone comment: Posts the summary as a separate comment |
Display preferences
These settings control how findings are displayed in the pull request.| Setting | Description | Options |
|---|---|---|
| Finding overflow | Determines how many findings appear before showing a “View all” option. | • None: All collapsed • 1, 3, or 5: Findings shown before “View all” • All: All findings expanded |
| Resolved overflow | Determines how many resolved findings appear before showing a “View all” option. | • None: All collapsed • 1, 3, or 5: Findings shown before “View all” • All: All findings expanded |
| Finding expansion | Controls which sections are expanded by default when opening a finding. Multiple selections allowed. | • Code • Description • Relevance, Evidence, Prompt |
Custom instructions
-
Add custom free-text instructions to guide how Qodo behaves.
Setting Description Issue finding agent Add custom prompts to guide issue detection and reporting behavior. Compliance agent Add custom prompts to guide compliance checks and policy enforcement. - Complete your selection and click Save.