Skip to main content
Otto is an AI teammate for your engineering workflow. It connects to GitHub or Azure DevOps and posts a native review on every pull request, and it can connect to Linear or Jira to clarify, plan, and implement tickets.

​
What Otto does

Reviews pull requests

A native review verdict, inline findings ranked P0–P3, and a merge-confidence score on every PR.

Configures per repository

An otto.yml sets review depth and instructions per path, ignores files, skips reviews, and limits approvals.

Gates merges

Require the Otto Review or Otto Approval check before a PR can merge.

Automates tickets

Clarify, plan, and implement Linear or Jira tickets, then respond to review feedback.

​
Where to start

Most teams start with reviews: connect a code host, open a pull request, and Otto reviews it. Follow the Quickstart, then set up your repositories and add an otto.yml when one repository needs different rules from the rest of your workspace.

​
What Otto is not

  • A replacement for human reviewers. Otto is a force multiplier; keep a human in the loop for anything critical.
  • An architect for complex system design or a fix for vague requirements.