Core concepts

Workspaces

A workspace (organization) is your team’s home in Otto. It holds your members, integrations, review settings, projects, and billing.

Role	Permissions
Owner	Full access, including billing and deleting the workspace
Admin	Manage integrations, review settings, and rules
Member	View-only access

Otto reviews pull requests with two layers of configuration:

Workspace settings in Settings → Reviews apply to every repository: whether automatic reviews run, the default review depth, and review instructions. See Workspace settings.
otto.yml, committed at a repository’s root, overrides those for one repository, down to individual paths. See otto.yml.

A repository’s OTTO.md or CLAUDE.md also guides the review. See Instructions.

Every review runs at one of three depths:

Depth	Use it for
Standard	Focused reviews for everyday changes.
Deep	Thorough reviews that trace changes across the codebase. New workspaces start here.
Max	The most thorough review, for critical code paths.

Deeper reviews cost more. Use otto.yml to spend depth where it matters. See Review depth.

Every finding has a severity:

Severity	Meaning
P0	Critical or blocking: data loss, security breach, outage, broken build.
P1	High-impact bug or security issue.
P2	Correctness, reliability, or missing-test issue to fix before merge.
P3	Non-blocking nitpick, style, or maintainability suggestion.

Beyond reviews, Otto can work tickets from Linear or Jira:

Rules choose which tickets Otto picks up. Without a rule, Otto picks up nothing.
Projects map a ticket project to the repository where Otto works.
The lifecycle (Clarify → Plan → Implement) takes a ticket to a pull request with human checkpoints.

Otto uses prepaid workspace credits and charges only for verified usage. See Billing.