> ## Documentation Index
> Fetch the complete documentation index at: https://autter.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect Autter to source control, issue trackers, notifications, and editor workflows.

Integrations give Autter the code, work-item context, and delivery channels needed for useful reviews.

<Frame caption="Placeholder: replace with approved integration artwork or a connected-tools screenshot.">
  <img src="https://mintcdn.com/autter/ZqVSJE8MeDV-Tn7Q/images/placeholders/integrations.svg?fit=max&auto=format&n=ZqVSJE8MeDV-Tn7Q&q=85&s=688d6877b593a484cd93e072c4a321cc" alt="Placeholder showing Autter connected to GitHub, GitLab, Jira, Linear, Slack, and VS Code" width="1200" height="620" data-path="images/placeholders/integrations.svg" />
</Frame>

## Available integrations

| Integration | Customer workflow                                       |
| ----------- | ------------------------------------------------------- |
| GitHub      | Review pull requests through the native GitHub workflow |
| GitLab      | Review merge requests through the GitLab workflow       |
| Jira        | Add linked issue context to code review                 |
| Linear      | Add linked issue context to code review                 |
| Slack       | Receive review and workflow notifications               |
| VS Code     | Use Autter in editor-adjacent workflows                 |

Integration availability can vary by plan. See [current pricing](https://www.autter.dev/pricing).

## Source control

Connect GitHub or GitLab first. This gives Autter access to the repository and proposed changes it needs to review.

<CardGroup cols={2}>
  <Card title="GitHub setup" icon="github" href="/guides/github-setup">
    Install the GitHub App, select repositories, and verify a pull request review.
  </Card>

  <Card title="GitLab setup" icon="gitlab" href="/guides/gitlab-setup">
    Authorize GitLab, select projects, and verify a merge request review.
  </Card>
</CardGroup>

## Issue context

Connect Jira or Linear when the issue contains acceptance criteria, constraints, or incident context that should influence review.

Before relying on linked context:

* confirm the pull request is linked to the correct issue
* keep acceptance criteria current
* avoid placing credentials or sensitive customer data in issue text
* verify that a review finding actually follows from the linked requirement

## Notifications

Use Slack when review events need visibility outside the source control provider. Keep notification routing focused so high-value review events are not buried in channel noise.

## Editor workflows

The public product lists a VS Code integration. The open source CLI also supports editor extensions that visualize AI authorship.

<Card title="AI blame" icon="code" href="/cli/ai-blame">
  Inspect line-level AI authorship in the terminal and supported editor extensions.
</Card>