Before you begin
You need:- an Autter account
- access to a GitHub repository or GitLab project
- permission to install or authorize the relevant integration
- a pull request or merge request you can open for verification
Plans and included review volumes can change. See current pricing before you roll Autter out across an organization.
Connect your first repository
Sign in to Autter
Open the Autter platform and sign in.
Connect GitHub or GitLab
Choose your source control provider and complete its authorization flow.
- GitHub
- GitLab
Install the Autter GitHub App on the account or organization that owns the repository.
Grant repository access
Select the repository or project Autter should review. Start with one active repository while you evaluate the feedback.
Open a pull request
Open a pull request or merge request in the connected repository. Autter starts the review from the proposed diff and available repository context.
Evaluate the first review
Check that the review gives the author enough context to act:- the affected code or behavior
- why the finding matters
- a proposed fix when Autter can provide one
- the severity or merge impact
Add a team rule
Autter supports team standards written in natural language. Define a small, testable rule such as:Payment handlers must verify the authenticated account owns the payment method before creating a charge.Apply the rule to the relevant repositories, then test it with a pull request that contains a representative change. See Custom rules for a safe rollout process.
Add AI authorship context
Install the Autter CLI when you also want line-level attribution for code written by coding agents.Troubleshoot the connection
If no review appears:- Confirm the repository is included in the integration’s access scope.
- Confirm the pull request targets the repository’s normal review branch.
- Check the Autter platform for a connection or review status.
- Reopen or update the pull request after fixing access.

