Installation & Setup
GitHub or GitLab users can follow the outlined steps to successfully enable Greptile within their repositories. Log in to your Greptile account or sign up via email, Google, Github, or GitLab. Ensure you have the required permissions to allow the AI code reviewer access to all or specific repos. Each platform offers a different procedure for integration.GitHub App installation
The GitHub app gives Greptile access to your repositories and lets it post reviews on pull requests.Open Code Providers
Go to Code Providers. Click Connect GitHub Cloud or Add Provider, then select GitHub.

Choose a GitHub account or organization
In GitHub, choose the account or organization where you want to install Greptile Apps. Use Configure for an existing installation.

Grant repository access
Select which repositories GitHub lets Greptile access:
- All repositories: Grant access to all current and future repositories in the account or organization.
- Only select repositories: Grant access only to selected repositories. Select at least one repository.

Link the GitHub organization in Greptile
After you click Install, GitHub automatically returns you to Greptile. Select the GitHub organization, then click Link.You can add more organizations later from Code Providers.

GitLab Integration
The GitLab integration uses a project or group access token. The token must use the Developer role and theapi scope.
Open GitLab integration
Go to Code Providers in Greptile and click Add Provider, then select GitLab. Greptile shows the token requirements and a field for the generated token.

Open access tokens in GitLab
In GitLab, open your project or group, then go to Settings → Access tokens.

Create the access token
Create a token with:
- Token name:
Greptile - Role:
Developer - Scope:
api - Expiration date: the latest allowed date

Repository Selection & Configuration
The following configuration steps are common to GitHub and GitLab:Enable repository indexing by Greptile
- Go to your team’s Repositories page
- Click Manage Repos (or Enable Repositories if no repos are enabled yet)
- Select the repos you want reviewed, then click Enable Repos (or use Enable All)

Configure PR Summary
Customize how Greptile summarizes pull requests:
- PR Summary: Include a text summary of the changes
- Confidence Score: Show confidence levels for each PR
- Issue Table: Show important changed files with ratings
- Sequence Diagram: Add a diagram of the changes

Control Review Behavior
Fine-tune what Greptile comments on in Code Review Settings:
- Strictness Level: Adjust how often Greptile comments
- Auto-review on new commits: Review new commits after a PR is opened
- Review draft pull requests: Review drafts before they are marked ready
- File change limit: Set the largest PR Greptile reviews automatically

Add Filters
Set when Greptile comments in Code Review Settings under Greptile Comments:
- Labels: Only review PRs with specific labels (e.g., “needs-review”)
- Authors: Include/exclude specific developers or bots
- Branches: Target specific branches (e.g., main, develop)
- Keywords: Trigger on PR title/description keywords

Create Your First Test PR
Try Greptile on a test pull request to see it in action:Wait for review (~3 minutes)
Greptile analyzes your PR with full codebase context and posts a comprehensive review.


You can trigger a code review manually by tagging @greptileai with a comment. This is helpful for reviewing older PRs from before Greptile was integrated.
What’s next?
- For developers: Learn how to work with Greptile reviews →
- For team admins: Set up organizations and teams →
- Deep dive: Understand the anatomy of a review →




