Settings
Configure your account, review options, severity filters, guardrails, and branch protection.
Configure your account and review settings from the Settings page.
Account
- Name: Editable display name
- Email: Synced from GitHub (read-only)
- Avatar: Synced from GitHub profile
API Key
Your API key is displayed in Settings. Use it for CLI authentication with paragon auth login.
Review Model Depth
Choose the model tier used for automatic PR reviews. Each tier has a different depth of analysis and credit cost.
| Model | Description | Credit Cost |
|---|---|---|
| Auto | Automatically adapts to PR complexity — uses a lighter model for simple changes and a deeper model for complex ones | Varies |
| Max | Deepest analysis with extended reasoning | 10x |
| MD | Balanced depth and speed | 3x |
| Fast | Quick scan for straightforward PRs | 1x |
Review Options
Configure what to include in automatic PR reviews:
Severity Filters
Control which types of issues are reported in your PR reviews.
Issue Severity Levels
Critical
Security vulnerabilities, data loss risks, crash-causing bugs
High
Major bugs, significant performance issues
Medium
Code quality issues, best practice violations
Low
Style issues, minor improvements, suggestions
At least one severity filter must remain enabled.
Guardrails
Guardrails are custom rules that Paragon enforces during every review. Unlike severity filters (which control what to report), guardrails define specific standards your code must meet.
Enabling Guardrails
Toggle guardrails on from the Configure page. When enabled, Paragon checks every PR against your active guardrails and flags violations alongside its standard review.
Templates
Paragon provides built-in guardrail templates you can activate with one click:
| Template | Category | Severity | Rule |
|---|---|---|---|
| File Length Limit | Code Quality | Warning | Files must be under 300 lines of code |
| Function Length Limit | Code Quality | Warning | Functions must be under 50 lines |
| No Console Logs | Code Quality | Error | No console.log statements in production code |
| No Any Types | Code Quality | Warning | TypeScript files must not use the "any" type |
| No Hardcoded Secrets | Security | Error | No hardcoded API keys, passwords, or secrets |
| JSDoc Required | Documentation | Warning | All public functions must have JSDoc comments |
| React Componentization | Code Quality | Warning | React components must be under 100 lines |
| Test File Required | Code Quality | Warning | New feature files must have corresponding test files |
Custom Guardrails
Create your own guardrails with:
- Name — A short label for the rule
- Description — What the rule checks for
- Rule — The specific standard to enforce (this is what the reviewer evaluates against)
- Category — Code Quality, Style, Security, or Documentation
- Severity — Error (must fix) or Warning (should fix)
Managing Guardrails
Each guardrail can be individually enabled or disabled without deleting it. Edit the name, description, rule, category, or severity at any time. Delete guardrails you no longer need.
Branch Protection
Prevent Paragon's agent from pushing directly to critical branches. When a branch is protected, the agent will create a separate branch and open a pull request instead of pushing directly.
Configuration
Branch protection is configured per repository:
- Go to the Configure page
- Scroll to Branch Protection
- Expand a repository
- Add branches to protect (e.g.,
main,master,production)
Patterns
Branch protection supports:
- Exact match — e.g.,
main,master,develop - Wildcard patterns — e.g.,
release/*,hotfix/*
Quick Add
Common branches (main, master, develop, staging, production) are suggested for quick selection when adding protection rules.