Getting Started with Optibot Configuration Settings

Customize how Optibot behaves across your repositories directly from the Optibot dashboard. Each repository gets its own configuration. Toggle features on or off, set review triggers, manage exclusions, and more. Changes take effect immediately with no files to commit or maintain.

Access your settings at: agents.getoptimal.ai → Configuration tab

Reviews

Control when and how Optibot reviews pull requests on this repository.

  • Auto review: Automatically review every PR on open. (Recommended)
  • Auto review on draft: Include draft PRs in automatic reviews.
  • Auto review on push: Trigger a new review whenever commits are pushed to an open PR.
  • Auto review after workflow: Trigger a review only after a CI workflow completes.
  • Allow approve: Allow Optibot to approve PRs that pass all checks.
  • Request changes: Post a blocking review as a formal GitHub “Request changes” instead of a plain comment. GitHub only.
  • Code suggestions: Allow Optibot to generate inline code suggestions during reviews.
  • Post outside-diff findings as comments: Post findings in files the PR doesn’t change as separate review comments instead of a section in the review body. GitHub only.
  • Skip files: Files or patterns excluded from the review process (e.g. *.md, docs/*).
  • Sensitivity: Controls strictness: Low, Medium, or High. Medium is recommended.
  • Excluded labels: PRs carrying any of these labels are skipped (e.g. wontfix).
  • Excluded users: PRs authored by these usernames are skipped (e.g. bot-account).
  • Suppress repeated issues: Issues already raised in a previous review are moved to a collapsible section.

→ Full review settings reference

Summary

Control when and how Optibot generates PR summaries.

  • Auto summary: Automatically generate a PR summary on open.
  • Auto summary on draft: Include draft PRs in automatic summaries.
  • Summary level: Controls the detail level: Basic or Detailed.
  • Excluded labels: PRs with these labels are skipped for automatic summaries.
  • Excluded users: PRs from these usernames are skipped for automatic summaries.

→ Full summary settings reference

Dependency Bundler

  • Enabled: Organizes and bundles incoming Dependabot PRs into a single consolidated PR. Reduces noise from individual dependency update PRs.

→ Dependency bundler settings

Monorepo Guidelines

Apply different review standards to different parts of your monorepo. Register per-directory markdown instruction files and Optibot automatically applies only the rules relevant to each PR’s changed directories.

  • Enabled: Turns per-directory review instructions on or off.
  • Paths: Repo-relative paths to your instruction markdown files. The file’s location determines which directory it governs.
  • Auto-detect: Give Optibot a glob like **/REVIEW.md and it discovers matching instruction files for you, so new services get covered without editing a list.
  • File-pattern instructions: Map a file type to an instruction file (e.g. *.proto → docs/protobuf-guideline.md) to scope rules by what kind of file changed rather than where it lives.

→ Monorepo guidelines reference

Shared Review Rules

Keep standards that apply across many repositories in one repository of markdown rule files. Optibot assigns each rule to the repositories it fits and applies them on every review. Shared rules are organization-wide and set up by an owner from agents.getoptimal.ai → Shared Review Rules.

  • Repository: The repository in your organization that holds the rule files.
  • Branch: The branch to read rules from. Defaults to the repository’s default branch.
  • Root directory: Only markdown files under this folder are treated as rules. Defaults to the whole repository.
  • Rule mapping: Which rules apply to each repository. Owners can exclude or add rules per repository.

→ Shared review rules guide

Other Settings

  • Enable CI fixer: Attempts to fix failed CI checks by opening fix PRs and/or suggesting remediation steps.
  • Tag to talk: When enabled, Optibot will only respond to comments that contain @optibot.
  • Guidelines URL: Path or URL pointing to your coding guidelines file inside the repository (e.g. docs/guidelines/README.md).

→ CI fixer settings

Review Fixer

Review Fixer settings are organization-wide rather than per-repository. Access them from agents.getoptimal.ai → Review Fixer.

  • Enable Review Fixer: Allow Optibot to automatically apply review comment fixes directly to your code when accepted.
  • Show “apply fixes” links: Add one-click “apply fixes” links to the footer of every review that found something. Off by default, so a fix only runs when your team deliberately triggers one. Turn this on if your team wants the one-click shortcut; otherwise trigger fixes explicitly with #optibot fix.

Note: Configuration tab settings (Reviews, Summary, Dependency Bundler, Monorepo Guidelines, and Other Settings above) are per-repository. If you manage multiple repositories, you’ll need to configure each one separately from the repository selector in the Settings tab. Review Fixer settings are the exception — they apply to your whole organization.